Non-posted write transactions for a computer bus

ABSTRACT

Systems and devices can include a controller and a command queue to buffer incoming write requests into the device. The controller can receive, from a client across a link, a non-posted write request (e.g., a deferred memory write (DMWr) request) in a transaction layer packet (TLP) to the command queue; determine that the command queue can accept the DMWr request; identify, from the TLP, a successful completion (SC) message that indicates that the DMWr request was accepted into the command queue; and transmit, to the client across the link, the SC message that indicates that the DMWr request was accepted into the command queue. The controller can receive a second DMWr request in a second TLP; determine that the command queue is full; and transmit a memory request retry status (MRS) message to be transmitted to the client in response to the command queue being full.

CROSS REFERENCE TO RELATED APPLICATION

Pursuant to 35 U.S.C. § 119(e), this disclosure claims the benefit ofU.S. Provisional Patent Application Ser. No. 62/836,288 filed on Apr.19, 2019, the entire contents of which are incorporated by referenceherein.

BACKGROUND

Central Processing Units (CPUs) perform general-purpose computing taskssuch as running application software and operating systems. Specializedcomputing tasks, such as graphics and image processing, are handled bygraphics processors, image processors, digital signal processors, andfixed-function accelerators. In today's heterogeneous machines, eachtype of processor is programmed in a different manner. The era of bigdata processing demands higher performance at lower energy as comparedwith today's general-purpose processors. Accelerators (either customfixed function units or tailored programmable units, for example) arehelping meet these demands.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating an embodiment of a blockdiagram for a computing system including a multicore processor inaccordance with embodiments of the present disclosure.

FIG. 2 is a schematic diagram of an example accelerator device inaccordance with embodiments of the present disclosure.

FIG. 3 is a schematic diagram of an example computer system thatincludes an accelerator and one or more computer processor chips coupledto the processor over a multi-protocol link.

FIG. 4 is a schematic diagram of an example work queue implementation inaccordance with embodiments of the present disclosure.

FIG. 5 is a schematic diagram of an example data streaming accelerator(DSA) device comprising multiple work queues that receive descriptorssubmitted over an I/O fabric interface.

FIGS. 6A-B are schematic diagrams illustrating example shared work queueimplementation scenarios in accordance with embodiments of the presentdisclosure.

FIGS. 7A-D are schematic diagrams illustrating an example deferredmemory write (DMWr) request and response message flow in accordance withembodiments of the present disclosure.

FIG. 8 is a process flow diagram for performing scalable worksubmissions in accordance with embodiments of the present disclosure.

FIG. 9A is a schematic diagram of a 64-bit DMWr packet definition inaccordance with embodiments of the present disclosure.

FIG. 9B is a schematic diagram of a 32-bit DMWr packet definition inaccordance with embodiments of the present disclosure.

FIG. 10 illustrates an embodiment of a computing system including aninterconnect architecture.

FIG. 11 illustrates an embodiment of a interconnect architectureincluding a layered stack.

FIG. 12 illustrates an embodiment of a request or packet to be generatedor received within an interconnect architecture.

FIG. 13 illustrates an embodiment of a transmitter and receiver pair foran interconnect architecture.

FIG. 14 illustrates another embodiment of a block diagram for acomputing system including a processor.

FIG. 15 illustrates another embodiment of a block diagram for acomputing system.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth,such as examples of specific types of processors and systemconfigurations, specific hardware structures, specific architectural andmicro architectural details, specific register configurations, specificinstruction types, specific system components, specificmeasurements/heights, specific processor pipeline stages and operationetc. in order to provide a thorough understanding of the presentdisclosure. It will be apparent, however, to one skilled in the art thatthese specific details need not be employed to practice the presentdisclosure. In other instances, well known components or methods, suchas specific and alternative processor architectures, specific logiccircuits/code for described algorithms, specific firmware code, specificinterconnect operation, specific logic configurations, specificmanufacturing techniques and materials, specific compilerimplementations, specific expression of algorithms in code, specificpower down and gating techniques/logic and other specific operationaldetails of computer system have not been described in detail in order toavoid unnecessarily obscuring the present disclosure.

Although the following embodiments may be described with reference toenergy conservation and energy efficiency in specific integratedcircuits, such as in computing platforms or microprocessors, otherembodiments are applicable to other types of integrated circuits andlogic devices. Similar techniques and teachings of embodiments describedherein may be applied to other types of circuits or semiconductordevices that may also benefit from better energy efficiency and energyconservation. For example, the disclosed embodiments are not limited todesktop computer systems or Ultrabooks™. And may be also used in otherdevices, such as handheld devices, tablets, other thin notebooks,systems on a chip (SOC) devices, and embedded applications. Someexamples of handheld devices include cellular phones, Internet protocoldevices, digital cameras, personal digital assistants (PDAs), andhandheld PCs. Embedded applications typically include a microcontroller,a digital signal processor (DSP), a system on a chip, network computers(NetPC), set-top boxes, network hubs, wide area network (WAN) switches,or any other system that can perform the functions and operations taughtbelow. Moreover, the apparatus', methods, and systems described hereinare not limited to physical computing devices, but may also relate tosoftware optimizations for energy conservation and efficiency. As willbecome readily apparent in the description below, the embodiments ofmethods, apparatus', and systems described herein (whether in referenceto hardware, firmware, software, or a combination thereof) are vital toa ‘green technology’ future balanced with performance considerations.

As computing systems are advancing, the components therein are becomingmore complex. As a result, the interconnect architecture to couple andcommunicate between the components is also increasing in complexity toensure bandwidth requirements are met for optimal component operation.Furthermore, different market segments demand different aspects ofinterconnect architectures to suit the market's needs. For example,servers require higher performance, while the mobile ecosystem issometimes able to sacrifice overall performance for power savings. Yet,it is a singular purpose of most fabrics to provide highest possibleperformance with maximum power saving. Below, a number of interconnectsare discussed, which would potentially benefit from aspects of thedisclosure described herein.

Referring to FIG. 1, an embodiment of a block diagram for a computingsystem including a multicore processor is depicted. Processor 100includes any processor or processing device, such as a microprocessor,an embedded processor, a digital signal processor (DSP), a networkprocessor, a handheld processor, an application processor, aco-processor, a system on a chip (SOC), or other device to execute code.Processor 100, in one embodiment, includes at least two cores-core 101and 102, which may include asymmetric cores or symmetric cores (theillustrated embodiment). However, processor 100 may include any numberof processing elements that may be symmetric or asymmetric.

In one embodiment, a processing element refers to hardware or logic tosupport a software thread. Examples of hardware processing elementsinclude: a thread unit, a thread slot, a thread, a process unit, acontext, a context unit, a logical processor, a hardware thread, a core,and/or any other element, which is capable of holding a state for aprocessor, such as an execution state or architectural state. In otherwords, a processing element, in one embodiment, refers to any hardwarecapable of being independently associated with code, such as a softwarethread, operating system, application, or other code. A physicalprocessor (or processor socket) typically refers to an integratedcircuit, which potentially includes any number of other processingelements, such as cores or hardware threads.

A core often refers to logic located on an integrated circuit capable ofmaintaining an independent architectural state, wherein eachindependently maintained architectural state is associated with at leastsome dedicated execution resources. In contrast to cores, a hardwarethread typically refers to any logic located on an integrated circuitcapable of maintaining an independent architectural state, wherein theindependently maintained architectural states share access to executionresources. As can be seen, when certain resources are shared and othersare dedicated to an architectural state, the line between thenomenclature of a hardware thread and core overlaps. Yet often, a coreand a hardware thread are viewed by an operating system as individuallogical processors, where the operating system is able to individuallyschedule operations on each logical processor.

Physical processor 100, as illustrated in FIG. 1, includes twocores—core 101 and 102. Here, core 101 and 102 are considered symmetriccores, i.e. cores with the same configurations, functional units, and/orlogic. In another embodiment, core 101 includes an out-of-orderprocessor core, while core 102 includes an in-order processor core.However, cores 101 and 102 may be individually selected from any type ofcore, such as a native core, a software managed core, a core adapted toexecute a native Instruction Set Architecture (ISA), a core adapted toexecute a translated Instruction Set Architecture (ISA), a co-designedcore, or other known core. In a heterogeneous core environment (i.e.asymmetric cores), some form of translation, such a binary translation,may be utilized to schedule or execute code on one or both cores. Yet tofurther the discussion, the functional units illustrated in core 101 aredescribed in further detail below, as the units in core 102 operate in asimilar manner in the depicted embodiment.

As depicted, core 101 includes two hardware threads 101 a and 101 b,which may also be referred to as hardware thread slots 101 a and 101 b.Therefore, software entities, such as an operating system, in oneembodiment potentially view processor 100 as four separate processors,i.e., four logical processors or processing elements capable ofexecuting four software threads concurrently. As alluded to above, afirst thread is associated with architecture state registers 101 a, asecond thread is associated with architecture state registers 101 b, athird thread may be associated with architecture state registers 102 a,and a fourth thread may be associated with architecture state registers102 b. Here, each of the architecture state registers (101 a, 101 b, 102a, and 102 b) may be referred to as processing elements, thread slots,or thread units, as described above. As illustrated, architecture stateregisters 101 a are replicated in architecture state registers 101 b, soindividual architecture states/contexts are capable of being stored forlogical processor 101 a and logical processor 101 b. In core 101, othersmaller resources, such as instruction pointers and renaming logic inallocator and renamer block 130 may also be replicated for threads 101 aand 101 b. Some resources, such as re-order buffers inreorder/retirement unit 135, ILTB 120, load/store buffers, and queuesmay be shared through partitioning. Other resources, such as generalpurpose internal registers, page-table base register(s), low-leveldata-cache and data-TLB 115, execution unit(s) 140, and portions ofout-of-order unit 135 are potentially fully shared.

Processor 100 often includes other resources, which may be fully shared,shared through partitioning, or dedicated by/to processing elements. InFIG. 1, an embodiment of a purely exemplary processor with illustrativelogical units/resources of a processor is illustrated. Note that aprocessor may include, or omit, any of these functional units, as wellas include any other known functional units, logic, or firmware notdepicted. As illustrated, core 101 includes a simplified, representativeout-of-order (OOO) processor core. But an in-order processor may beutilized in different embodiments. The OOO core includes a branch targetbuffer 120 to predict branches to be executed/taken and aninstruction-translation buffer (I-TLB) 120 to store address translationentries for instructions.

Core 101 further includes decode module 125 coupled to fetch unit 120 todecode fetched elements. Fetch logic, in one embodiment, includesindividual sequencers associated with thread slots 101 a, 101 b,respectively. Usually core 101 is associated with a first ISA, whichdefines/specifies instructions executable on processor 100. Oftenmachine code instructions that are part of the first ISA include aportion of the instruction (referred to as an opcode), whichreferences/specifies an instruction or operation to be performed. Decodelogic 125 includes circuitry that recognizes these instructions fromtheir opcodes and passes the decoded instructions on in the pipeline forprocessing as defined by the first ISA. For example, as discussed inmore detail below decoders 125, in one embodiment, include logicdesigned or adapted to recognize specific instructions, such astransactional instruction. As a result of the recognition by decoders125, the architecture or core 101 takes specific, predefined actions toperform tasks associated with the appropriate instruction. It isimportant to note that any of the tasks, blocks, operations, and methodsdescribed herein may be performed in response to a single or multipleinstructions; some of which may be new or old instructions. Notedecoders 126, in one embodiment, recognize the same ISA (or a subsetthereof). Alternatively, in a heterogeneous core environment, decoders126 recognize a second ISA (either a subset of the first ISA or adistinct ISA).

In one example, allocator and renamer block 130 includes an allocator toreserve resources, such as register files to store instructionprocessing results. However, threads 101 a and 101 b are potentiallycapable of out-of-order execution, where allocator and renamer block 130also reserves other resources, such as reorder buffers to trackinstruction results. Unit 130 may also include a register renamer torename program/instruction reference registers to other registersinternal to processor 100. Reorder/retirement unit 135 includescomponents, such as the reorder buffers mentioned above, load buffers,and store buffers, to support out-of-order execution and later in-orderretirement of instructions executed out-of-order.

Scheduler and execution unit(s) block 140, in one embodiment, includes ascheduler unit to schedule instructions/operation on execution units.For example, a floating point instruction is scheduled on a port of anexecution unit that has an available floating point execution unit.Register files associated with the execution units are also included tostore information instruction processing results. Exemplary executionunits include a floating point execution unit, an integer executionunit, a jump execution unit, a load execution unit, a store executionunit, and other known execution units.

Lower level data cache and data translation buffer (D-TLB) 150 arecoupled to execution unit(s) 140. The data cache is to store recentlyused/operated on elements, such as data operands, which are potentiallyheld in memory coherency states. The D-TLB is to store recentvirtual/linear to physical address translations. As a specific example,a processor may include a page table structure to break physical memoryinto a plurality of virtual pages.

Here, cores 101 and 102 share access to higher-level or further-outcache, such as a second level cache associated with on-chip interface110. Note that higher-level or further-out refers to cache levelsincreasing or getting further way from the execution unit(s). In oneembodiment, higher-level cache is a last-level data cache—last cache inthe memory hierarchy on processor 100—such as a second or third leveldata cache. However, higher level cache is not so limited, as it may beassociated with or include an instruction cache. A trace cache—a type ofinstruction cache—instead may be coupled after decoder 125 to storerecently decoded traces. Here, an instruction potentially refers to amacro-instruction (i.e. a general instruction recognized by thedecoders), which may decode into a number of micro-instructions(micro-operations).

In the depicted configuration, processor 100 also includes on-chipinterface module 110. Historically, a memory controller, which isdescribed in more detail below, has been included in a computing systemexternal to processor 100. In this scenario, on-chip interface 11 is tocommunicate with devices external to processor 100, such as systemmemory 175, a chipset (often including a memory controller hub toconnect to memory 175 and an I/O controller hub to connect peripheraldevices), a memory controller hub, a northbridge, or other integratedcircuit. And in this scenario, bus 105 may include any knowninterconnect, such as multi-drop bus, a point-to-point interconnect, aserial interconnect, a parallel bus, a coherent (e.g. cache coherent)bus, a layered protocol architecture, a differential bus, and a GTL bus.

Memory 175 may be dedicated to processor 100 or shared with otherdevices in a system. Common examples of types of memory 175 includeDRAM, SRAM, non-volatile memory (NV memory), and other known storagedevices. Note that device 180 may include a graphic accelerator,processor or card coupled to a memory controller hub, data storagecoupled to an I/O controller hub, a wireless transceiver, a flashdevice, an audio controller, a network controller, or other knowndevice.

Recently however, as more logic and devices are being integrated on asingle die, such as SOC, each of these devices may be incorporated onprocessor 100. For example in one embodiment, a memory controller hub ison the same package and/or die with processor 100. Here, a portion ofthe core (an on-core portion) 110 includes one or more controller(s) forinterfacing with other devices such as memory 175 or a graphics device180. The configuration including an interconnect and controllers forinterfacing with such devices is often referred to as an on-core (orun-core configuration). As an example, on-chip interface 110 includes aring interconnect for on-chip communication and a high-speed serialpoint-to-point link 105 for off-chip communication. Yet, in the SOCenvironment, even more devices, such as the network interface,co-processors, memory 175, graphics processor 180, and any other knowncomputer devices/interface may be integrated on a single die orintegrated circuit to provide small form factor with high functionalityand low power consumption.

In one embodiment, processor 100 is capable of executing a compiler,optimization, and/or translator code 177 to compile, translate, and/oroptimize application code 176 to support the apparatus and methodsdescribed herein or to interface therewith. A compiler often includes aprogram or set of programs to translate source text/code into targettext/code. Usually, compilation of program/application code with acompiler is done in multiple phases and passes to transform hi-levelprogramming language code into low-level machine or assembly languagecode. Yet, single pass compilers may still be utilized for simplecompilation. A compiler may utilize any known compilation techniques andperform any known compiler operations, such as lexical analysis,preprocessing, parsing, semantic analysis, code generation, codetransformation, and code optimization.

Larger compilers often include multiple phases, but most often thesephases are included within two general phases: (1) a front-end, i.e.generally where syntactic processing, semantic processing, and sometransformation/optimization may take place, and (2) a back-end, i.e.generally where analysis, transformations, optimizations, and codegeneration takes place. Some compilers refer to a middle, whichillustrates the blurring of delineation between a front-end and back endof a compiler. As a result, reference to insertion, association,generation, or other operation of a compiler may take place in any ofthe aforementioned phases or passes, as well as any other known phasesor passes of a compiler. As an illustrative example, a compilerpotentially inserts operations, calls, functions, etc. in one or morephases of compilation, such as insertion of calls/operations in afront-end phase of compilation and then transformation of thecalls/operations into lower-level code during a transformation phase.Note that during dynamic compilation, compiler code or dynamicoptimization code may insert such operations/calls, as well as optimizethe code for execution during runtime. As a specific illustrativeexample, binary code (already compiled code) may be dynamicallyoptimized during runtime. Here, the program code may include the dynamicoptimization code, the binary code, or a combination thereof.

Similar to a compiler, a translator, such as a binary translator,translates code either statically or dynamically to optimize and/ortranslate code. Therefore, reference to execution of code, applicationcode, program code, or other software environment may refer to: (1)execution of a compiler program(s), optimization code optimizer, ortranslator either dynamically or statically, to compile program code, tomaintain software structures, to perform other operations, to optimizecode, or to translate code; (2) execution of main program code includingoperations/calls, such as application code that has beenoptimized/compiled; (3) execution of other program code, such aslibraries, associated with the main program code to maintain softwarestructures, to perform other software related operations, or to optimizecode; or (4) a combination thereof.

FIG. 2 is a schematic diagram of an example accelerator device 200 inaccordance with embodiments of the present disclosure. As illustrated inFIG. 2, in one implementation, an accelerator includes PCI configurationregisters 204 and MMIO registers 210 which may be programmed to provideaccess to device backend resources 212. In one implementation, the baseaddresses for the MMIO registers 210 are specified by a set of BaseAddress Registers (BARs) 202 in PCI configuration space. Unlike previousimplementations, one implementation of the data streaming accelerator(DSA) described herein does not implement multiple channels or PCIfunctions, so there is only one instance of each register in a device.However, there may be more than one DSA device in a single platform.

An implementation may provide additional performance or debug registersthat are not described here. Any such registers should be consideredimplementation specific.

The PCI configuration space accesses are performed as aligned 1-, 2-, or4-byte accesses. See the PCI Express Base Specification for rules onaccessing unimplemented registers and reserved bits in PCI configurationspace.

MMIO space accesses to the BAR0 region (capability, configuration, andstatus registers) is performed as aligned 1-, 2-, 4- or 8-byte accesses.The 8-byte accesses should only be used for 8-byte registers. Softwareshould not read or write unimplemented registers. The MMIO spaceaccesses to the BAR 2 and BAR 4 regions should be performed as 64-byteaccesses, using the ENQCMD, ENQCMDS, or MOVDIR64B instructions(described in detail below). ENQCMD or ENQCMDS should be used to accessa work queue that is configured as shared (SWQ), and MOVDIR64B must beused to access a work queue that is configured as dedicated (DWQ).

One implementation of the DSA PCI configuration space implements three64-bit BARs 202. The Device Control Register (BAR0) is a 64-bit BAR thatcontains the physical base address of device control registers. Theseregisters provide information about device capabilities, controls toconfigure and enable the device, and device status. The size of the BAR0region is dependent on the size of the Interrupt Message Storage 208.The size is 32 KB plus the number of Interrupt Message Storage entries208 times 16, rounded up to the next power of 2. For example, if thedevice supports 1024 Interrupt Message Storage entries 208, theInterrupt Message Storage is 16 KB, and the size of BAR0 is 64 KB.

BAR2 is a 64-bit BAR that contains the physical base address of thePrivileged and Non-Privileged Portals. Each portal is 64-bytes in sizeand is located on a separate 4 KB page. This allows the portals to beindependently mapped into different address spaces using CPU pagetables. The portals are used to submit descriptors to the device. ThePrivileged Portals are used by kernel-mode software, and theNon-Privileged Portals are used by user-mode software. The number ofNon-Privileged Portals is the same as the number of work queuessupported. The number of Privileged Portals is Number-of-Work Queues(WQs)×(MSI-X-table-size−1). The address of the portal used to submit adescriptor allows the device to determine which WQ to place thedescriptor in, whether the portal is privileged or non-privileged, andwhich MSI-X table entry may be used for the completion interrupt. Forexample, if the device supports 8 WQs, the WQ for a given descriptor is(Portal-address >>12) & 0x7. If Portal-address >>15 is 0, the portal isnon-privileged; otherwise it is privileged and the MSI-X 206 table indexused for the completion interrupt is Portal-address >>15. Bits 5:0 mustbe 0. Bits 11:6 are ignored; thus any 64-byte-aligned address on thepage can be used with the same effect.

Descriptor submissions using a Non-Privileged Portal are subject to theoccupancy threshold of the WQ, as configured using a work queueconfiguration (WQCFG) register. Descriptor submissions using aPrivileged Portal are not subject to the threshold. Descriptorsubmissions to a SWQ must be submitted using ENQCMD or ENQCMDS. Anyother write operation to a SWQ portal is ignored. Descriptor submissionsto a DWQ must be submitted using a 64-byte write operation. Softwareuses MOVDIR64B, to guarantee a non-broken 64-byte write. An ENQCMD orENQCMDS to a disabled or dedicated WQ portal returns Retry. Any otherwrite operation to a DWQ portal is ignored. Any read operation to theBAR2 address space returns all is. Kernel-mode descriptors should besubmitted using Privileged Portals in order to receive completioninterrupts. If a kernel-mode descriptor is submitted using aNon-Privileged Portal, no completion interrupt can be requested.User-mode descriptors may be submitted using either a Privileged or aNon-Privileged Portal.

The number of portals in the BAR2 region is the number of WQs supportedby the device times the MSI-X 206 table size. The MSI-X table size istypically the number of WQs plus 1. So, for example, if the devicesupports 8 WQs, the useful size of BAR2 would be 8×9×4 KB=288 KB. Thetotal size of BAR2 would be rounded up to the next power of two, or 512KB.

BAR4 is a 64-bit BAR that contains the physical base address of theGuest Portals. Each Guest Portal is 64-bytes in size and is located in aseparate 4 KB page. This allows the portals to be independently mappedinto different address spaces using CPU extended page tables (EPT). Ifthe Interrupt Message Storage Support field in GENCAP is 0, this BAR isnot implemented.

The Guest Portals may be used by guest kernel-mode software to submitdescriptors to the device. The number of Guest Portals is the number ofentries in the Interrupt Message Storage times the number of WQssupported. The address of the Guest Portal used to submit a descriptorallows the device to determine the WQ for the descriptor and also theInterrupt Message Storage entry to use to generate a completioninterrupt for the descriptor completion (if it is a kernel-modedescriptor, and if the Request Completion Interrupt flag is set in thedescriptor). For example, if the device supports 8 WQs, the WQ for agiven descriptor is (Guest-portal-address >>12) & 0x7, and the interrupttable entry index used for the completion interrupt isGuest-portal-address >>15.

In one implementation, MSI-X is the only PCIe interrupt capability thatDSA provides and DSA does not implement legacy PCI interrupts or MSI.Details of this register structure are in the PCI Express specification.

In one implementation, three PCI Express capabilities control addresstranslation. Only certain combinations of values for these capabilitiesmay be supported, as shown in Table 1. The values are checked at thetime the Enable bit in General Control Register (GENCTRL) is set to 1.

TABLE 1 Supported combinations of capabilities and associated values.PASID ATS PRS Operation 1 1 1 Virtual or physical addresses may be used,depending on IOMMU configuration. Addresses are translated using thePASID in the descriptor. This is the recommended mode. This mode must beused to allow user-mode access to the device or to allow sharing amongmultiple guests in a virtualized system. 0 1 0 Only physical addressesmay be used. Addresses are translated using the BDF of the device andmay be GPA or HPA, depending on IOMMU configuration. The PASID in thedescriptor is ignored. This mode may be used when address translation isenabled in the IOMMU but the device is only used by the kernel or by asingle guest kernel in a virtualized 0 0 0 All memory accesses areUntranslated Accesses. Only physical addresses may be used. This modeshould be used only if IOMMU address translation is disabled. 0 0 1 Notallowed. If software attempts to enable the 0 1 1 device with one ofthese configurations, an error 1 0 0 is reported and the device is notenabled. 1 0 1 1 1 0

If any of these capabilities are changed by software while the device isenabled, the device may halt and an error is reported in the SoftwareError Register.

In one implementation, software configures the PASID capability tocontrol whether the device uses PASID to perform address translation. IfPASID is disabled, only physical addresses may be used. If PASID isenabled, virtual or physical addresses may be used, depending on IOMMUconfiguration. If PASID is enabled, both address translation services(ATS) and page request services (PRS) should be enabled.

In one implementation, software configures the ATS capability to controlwhether the device should translate addresses before performing memoryaccesses. If address translation is enabled in the IOMMU 2810, ATS mustbe enabled in the device to obtain acceptable system performance. Ifaddress translation is not enabled in the IOMMU 2810, ATS must bedisabled. If ATS is disabled, only physical addresses may be used andall memory accesses are performed using Untranslated Accesses. ATS mustbe enabled if PASID is enabled.

In one implementation, software configures the PRS capability to controlwhether the device can request a page when an address translation fails.PRS must be enabled if PASID is enabled, and must be disabled if PASIDis disabled.

Some implementations utilize a virtual memory space that is seamlesslyshared between one or more processor cores, accelerator devices, and/orother types of processing devices (e.g., I/O devices). In particular,one implementation utilizes a shared virtual memory (SVM) architecturein which the same virtual memory space is shared between cores,accelerator devices, and/or other processing devices. In addition, someimplementations include heterogeneous forms of physical system memorywhich are addressed using a common virtual memory space. Theheterogeneous forms of physical system memory may use different physicalinterfaces for connecting with the DSA architectures. For example, anaccelerator device may be directly coupled to local accelerator memorysuch as a high bandwidth memory (HBM) and each core may be directlycoupled to a host physical memory such as a dynamic random access memory(DRAM). In this example, the shared virtual memory (SVM) is mapped tothe combined physical memory of the HBM and DRAM so that theaccelerator, processor cores, and/or other processing devices can accessthe HBM and DRAM using a consistent set of virtual memory addresses.

These and other features accelerators are described in detail below. Byway of a brief overview, different implementations may include one ormore of the following infrastructure features:

Shared Virtual Memory (SVM):

some implementations support SVM which allows user level applications tosubmit commands to DSA directly with virtual addresses in thedescriptors. DSA may support translating virtual addresses to physicaladdresses using an input/output memory management unit (IOMMU) includinghandling page faults. The virtual address ranges referenced by adescriptor may span multiple pages spread across multiple heterogeneousmemory types. Additionally, one implementation also supports the use ofphysical addresses, as long as data buffers are contiguous in physicalmemory.

Partial Descriptor Completion:

with SVM support, it is possible for an operation to encounter a pagefault during address translation. In some cases, the device mayterminate processing of the corresponding descriptor at the point wherethe fault is encountered and provide a completion record to softwareindicating partial completion and the faulting information to allowsoftware to take remedial actions and retry the operation afterresolving the fault.

Batch Processing:

some implementations support submitting descriptors in a “batch.” Abatch descriptor points to a set of virtually contiguous workdescriptors (i.e., descriptors containing actual data operations). Whenprocessing a batch descriptor, DSA fetches the work descriptors from thespecified memory and processes them.

Stateless Device:

descriptors in one implementation are designed so that all informationrequired for processing the descriptor comes in the descriptor payloaditself. This allows the device to store little client-specific statewhich improves its scalability. One exception is the completioninterrupt message which, when used, is configured by trusted software.

Cache Allocation Control:

this allows applications to specify whether to write to cache or bypassthe cache and write directly to memory. In one implementation,completion records are always written to cache.

Shared Work Queue (SWQ) Support:

as described in detail below, some implementations support scalable worksubmission through Shared Work Queues (SWQ) using the Enqueue Command(ENQCMD) and Enqueue Command as Supervisor (ENQCMDS) instructions. Inthis implementation, the SWQ is shared by multiple applications. TheENQCMD can be executed from a user (non ring 0) or supervisor (ring 0)privilege levels. The ENQCMDS can be executed from a supervisor (ring 0)privilege level.

Dedicated Work Queue (DWQ) Support:

in some implementations, there is support for high-throughput worksubmission through Dedicated Work queues (DWQ) using MOVDIR64Binstruction. In this implementation the DWQ is dedicated to oneparticular application.

Qos Support:

some implementations allow a quality of service (QoS) level to bespecified for each work queue (e.g., by a Kernel driver). It may thenassign different work queues to different applications, allowing thework from different applications to be dispatched from the work queueswith different priorities. The work queues can be programmed to usespecific channels for fabric QoS.

Biased Cache Coherence Mechanisms

One implementation improves the performance of accelerators withdirectly attached memory such as stacked DRAM or HBM, and simplifiesapplication development for applications which make use of acceleratorswith directly attached memory. This implementation allows acceleratorattached memory to be mapped as part of system memory, and accessedusing Shared Virtual Memory (SVM) technology (such as that used incurrent IOMMU implementations), but without suffering the typicalperformance drawbacks associated with full system cache coherence.

The ability to access accelerator attached memory as part of systemmemory without onerous cache coherence overhead provides a beneficialoperating environment for accelerator offload. The ability to accessmemory as part of the system address map allows host software to setupoperands, and access computation results, without the overhead oftraditional I/O DMA data copies. Such traditional copies involve drivercalls, interrupts and memory mapped I/O (MMIO) accesses that are allinefficient relative to simple memory accesses. At the same time, theability to access accelerator attached memory without cache coherenceoverheads can be critical to the execution time of an offloadedcomputation. In cases with substantial streaming write memory traffic,for example, cache coherence overhead can cut the effective writebandwidth seen by an accelerator in half. The efficiency of operandsetup, the efficiency of results access and the efficiency ofaccelerator computation all play a role in determining how wellaccelerator offload will work. If the cost of offloading work (e.g.,setting up operands; getting results) is too high, offloading may notpay off at all, or may limit the accelerator to only very large jobs.The efficiency with which the accelerator executes a computation canhave the same effect.

One implementation applies different memory access and coherencetechniques depending on the entity initiating the memory access (e.g.,the accelerator, a core, etc.) and the memory being accessed (e.g., hostmemory or accelerator memory). These techniques are referred togenerally as a “Coherence Bias” mechanism which provides for acceleratorattached memory two sets of cache coherence flows, one optimized forefficient accelerator access to its attached memory, and a secondoptimized for host access to accelerator attached memory and sharedaccelerator/host access to accelerator attached memory. Further, itincludes two techniques for switching between these flows, one driven byapplication software, and another driven by autonomous hardware hints.In both sets of coherence flows, hardware maintains full cachecoherence.

FIG. 3 is a schematic diagram of an example computer system 300 thatincludes an accelerator and one or more computer processor chips coupledto the processor over a multi-protocol link. As illustrated generally inFIG. 3, one implementation applies to computer systems which include anaccelerator 302 and one or more computer processor chips with processorcores and I/O circuitry 304, where the accelerator 302 is coupled to theprocessor over a multi-protocol link 314. In one implementation, themulti-protocol link 314 is a dynamically multiplexed link supporting aplurality of different protocols including, but not limited to thosedetailed above. It should be noted, however, that the underlyingprinciples of the invention are not limited to any particular set ofprotocols. In addition, note that the accelerator 302 and Core I/O 304may be integrated on the same semiconductor chip or differentsemiconductor chips, depending on the implementation.

In the illustrated implementation, an accelerator memory bus 316 couplesthe accelerator 302 to an accelerator memory 306 and a separate hostmemory bus 318 couples the core I/O 304 to a host memory 308. Asmentioned, the accelerator memory 306 may comprise a High BandwidthMemory (HBM) or a stacked DRAM (some examples of which are describedherein) and the host memory 308 may comprise a DRAM such as aDouble-Data Rate synchronous dynamic random access memory (e.g., DDR3SDRAM, DDR4 SDRAM, etc.). However, the underlying principles of theinvention are not limited to any particular types of memory or memoryprotocols.

In one implementation, both the accelerator 302 and “host” softwarerunning on the processing cores within the processor chips 304 accessthe accelerator memory 306 using two distinct sets of protocol flows,referred to as “Host Bias” flows and “Device Bias” flows. As describedbelow, one implementation supports multiple options for modulatingand/or choosing the protocol flows for specific memory accesses.

The Coherence Bias flows are implemented, in part, on two protocollayers on the multi-protocol link 314 between the accelerator 302 andone of the processor chips 304: a CAC protocol layer and a MA protocollayer. In one implementation, the Coherence Bias flows are enabled by:(a) using existing opcodes in the CAC protocol in new ways, (b) theaddition of new opcodes to an existing MA standard and (c) the additionof support for the MA protocol to a multi-protocol link 302 (prior linksinclude only CAC and PCDI). Note that the multi-protocol link is notlimited to supporting just CAC and MA; in one implementation, it issimply required to support at least those protocols.

As used herein, the “Host Bias” flows, illustrated in FIG. 3 are a setof flows that funnel all requests to accelerator memory 306 through thestandard coherence controller 312 in the processor chip 304 to which theaccelerator 302 is attached, including requests from the acceleratoritself. This causes the accelerator 302 to take a circuitous route toaccess its own memory, but allows accesses from both the accelerator 302and processor core I/O 304 to be maintained as coherent using theprocessor's standard coherence controllers 312. In one implementation,the flows use CAC opcodes to issues requests over the multi-protocollink to the processor's coherence controllers 312, in the same orsimilar manner to the way processor cores 312 issue requests to thecoherence controllers 312. For example, the processor chip's coherencecontrollers 312 may issue UPI and CAC coherence messages (e.g., snoops)that result from requests from the accelerator 302 to all peer processorcore chips (e.g., 304) and internal processor agents on theaccelerator's behalf, just as they would for requests from a processorcore 304. In this manner, coherency is maintained between the dataaccessed by the accelerator 302 and processor cores I/O 304.

In one implementation, the coherence controllers 312 also conditionallyissue memory access messages to the accelerator's memory controller 310over the multi-protocol link 314. These messages are similar to themessages that the coherence controllers 312 send to the memorycontrollers that are local to their processor die, and include newopcodes that allow data to be returned directly to an agent internal tothe accelerator 302, instead of forcing data to be returned to theprocessor's coherence controller 312 of the multi-protocol link 314, andthen returned to the accelerator 302 as a CAC response over themulti-protocol link 314.

In one implementation of “Host Bias” mode shown in FIG. 3, all requestsfrom processor cores 304 that target accelerator attached memory 306 aresent directly to the processors coherency controllers 312, just as theywere they targeting normal host memory 308. The coherence controllers312 may apply their standard cache coherence algorithms and send theirstandard cache coherence messages, just as they do for accesses from theaccelerator 302, and just as they do for accesses to normal host memory308. The coherence controllers 312 also conditionally send MA commandsover the multi-protocol link 314 for this class of requests, though inthis case, the MA flows return data across the multiprotocol link 314.

FIG. 4 is a schematic diagram of an example work queue implementation400 in accordance with embodiments of the present disclosure. In someimplementations, Work Queues (WQ) hold “descriptors” submitted bysoftware, arbiters used to implement quality of service (QoS) andfairness policies, processing engines for processing the descriptors, anaddress translation and caching interface, and a memory read/writeinterface. Descriptors define the scope of work to be done. Asillustrated in FIG. 4, in one implementation, there are two differenttypes of work queues: dedicated work queues 402 and shared work queues404. Dedicated work queues 402 store descriptors for a singleapplication 416 while shared work queues 404 store descriptors submittedby multiple applications 410-414. A hardware interface/arbiter 406dispatches descriptors from the work queues 402-404 to the acceleratorprocessing engines 408 in accordance with a specified arbitration policy(e.g., based on the processing requirements of each application 410-416and QoS/fairness policies).

Shared Work Queue Support on Endpoint Devices

FIG. 4 illustrates the concept of a Shared Work Queue (SWQ), whichallows multiple non-cooperating software agents (applications 410-414)to submit work through a shared work queue 404, utilizing the ENQCMD/Sinstructions described herein.

The following considerations are applicable to endpoint devicesimplementing Shared Work Queues (SWQ).

SWQs and its enumeration: A device physical function (PF) may supportone or more SWQs. Each SWQ is accessible for Enqueue non-posted writesthrough a 64-byte aligned and sized register (referred here on asSWQ_REG) in the device MMIO address range. Each such SWQ_REG on a deviceis recommended to be located on a unique system page size (4 KB) region.The device driver for the device is responsible forreporting/enumerating the SWQ capability, the number of SWQs supportedand the corresponding SWQ_REG addresses to software through appropriatesoftware interfaces. The driver may also optionally report the depth ofthe SWQ supported for software tuning or informational purposes(although this is not required for functional correctness). For devicessupporting multiple physical functions, it is recommended to supportindependent SWQs for each physical function.

SWQ support on Single Root I/O Virtualization (SR-IOV) devices: Devicessupporting SR-IOV may support independent SWQs for each Virtual Function(VF), exposed through SWQ_REGs in respective VF base address registers(BARs). This design point allows for maximum performance isolation forwork submission across VFs, and may be appropriate for a small tomoderate number of VFs. For devices supporting large number of VFs(where independent SWQ per VF is not practical), a single SWQ may beshared across multiple VFs. Even in this case, each VF has its ownprivate SWQ_REGs in its VF BARs, except they are backed by a common SWQacross the VFs sharing the SWQ. For such device designs, which VFs sharea SWQ may be decided statically by the hardware design, or the mappingbetween a given VF's SWQ_REG to SWQ instance may be dynamicallysetup/torn-down through the Physical Function and its driver. Devicedesigns sharing SWQ across VFs need to pay special attention to QoS andprotection against denial of service attacks as described later in thissection. When sharing SWQs across VFs, care must be taken in the devicedesign to identify which VF received an Enqueue request accepted to SWQ.When dispatching the work requests from the SWQ, the device should makesure upstream requests are properly tagged with the Requester-ID(Bus/Device/Function #) of the respective VF (in addition to the PASIDthat was conveyed in the Enqueue request payload).

Enqueue non-posted write address: Endpoint devices supporting SWQs arerequired to accept Enqueue non-posted writes to any addresses routedthrough their PF or VF memory BARs. For any Enqueue non-posted writerequest received by an endpoint device to an address that is not anSWQ_REG address, the device may be required to not treat this as anerror (e.g., Malformed TLP, etc.) and instead return completion with acompletion status of Retry (MRS). This may be done to ensureunprivileged (ring-3 or ring-0 VMX guest) software use of ENQCMD/Sinstructions to erroneously or maliciously issue Enqueue-stores to a nonSWQ_REG addresses on a SWQ-capable device cannot result in non-fatal orfatal error reporting with platform-specific error handlingconsequences.

Non-Enqueue Request handling to SWQ_REGs: Endpoint devices supportingSWQs may silently drop non-Enqueue requests (normal memory writes andreads) to the SWQ_REG addresses without treating them as fatal ornon-fatal errors. Read requests to the SWQ_REG addresses may return asuccessful completion response (as opposed to UR or CA) with a value ofall is for the requested data bytes. Normal memory (posted) writerequests to SWQ_REG addresses are simply dropped without action by theendpoint device. This may be done to ensure unprivileged software cannotgenerate normal read and write requests to the SWQ_REG address toerroneously or maliciously cause non-fatal or fatal error reporting withplatform-specific error handling consequences.

SWQ queue depth and storage: SWQ queue depth and storage is deviceimplementation specific. Device designs should ensure sufficient queuedepth is supported for the SWQ to achieve maximum utilization of thedevice. Storage for the SWQ may be implemented on the device. Integrateddevices on the SoC may utilize stolen main memory (non-OS visibleprivate memory reserved for device use) as a spill buffer for the SWQallowing for larger SWQ queue-depths than possible with on-devicestorage. For such designs, the use of a spill buffer is transparent tosoftware, with device hardware deciding when to spill (versus drop theEnqueue request and send a Retry completion status), fetch from thespill buffer for command execution, and maintain any command-specificordering requirements. For all purposes, such spill buffer usage isequivalent to a discrete device using local device-attached DRAM for SWQstorage. Device designs with a spill buffer in stolen memory must takeextreme care to make sure that such stolen memory is protected from anyaccesses other than spill buffer read and writes by the device for whichit is allocated for.

Non-blocking SWQ behavior: For performance reasons, deviceimplementations should respond quickly to Enqueue non-posted writerequests with Success or Retry completion status, and not block Enqueuecompletions for SWQ capacity to be freed-up to accept the request. Thedecision to accept or reject an Enqueue request to the SWQ could bebased on capacity, QoS/occupancy or any other policies. Some example QoSconsiderations are described next.

SWQ QoS considerations: For an Enqueue non-posted write targeting aSWQ_REG address, the endpoint device may apply admission control todecide to accept the request to the respective SWQ (and send asuccessful completion status) or drop it (and send a Retry completionstatus). The admission control may be device and usage specific, and thespecific policies supported/enforced by hardware may be exposed tosoftware through the Physical Function (PF) driver interfaces. Becausethe SWQ is a shared resource with multiple producer clients, deviceimplementations must ensure adequate protection againstdenial-of-service attacks across producers. QoS for SWQ refers only toacceptance of work requests (through enqueue requests) to the SWQ, andis orthogonal to any QoS applied by the device hardware on how QoS isapplied to share the execution resources of the device when processingwork requests submitted by different producers. Some example approachesare described below for configuring endpoint devices to enforceadmission policies for accepting Enqueue requests to SWQ. These aredocumented for illustration purposes only and the exact implementationchoices will be device specific.

These CPU instructions produce an atomic non-posted write transaction (awrite transaction for which a completion response is returned back tothe CPU). The non-posted write transaction is address routed like anynormal MMIO write to the target device. The non-posted write transactioncarries with it the following information:

a. Identity of the address space of the client that executed thisinstruction. For this disclosure, we use the “Process Address SpaceIdentifier” (PASID) as the client address-space identity. Depending onthe software usage, PASID can be used for any of the type of clients(process, container, VM, etc.). It is possible for other implementationof this invention to use different identification schemes. ENQCMDinstruction use the PASID associated with the current software thread(something the OS is expected to save/restore using XSAVES/XRSTORSinstructions on thread context switches). ENQCMDS instruction allows theprivileged software executing this instruction to specify the PASID aspart of the source operand for ENQCMDS instruction.

b. Privilege (supervisor or user) of the client that executed thisinstruction. Execution of ENQCMD always indicates user permission.ENQCMDS allows supervisor-mode software executing it to specify eitheruser privilege (if it is executing it on behalf of some ring-3 client),or supervisor privilege (to indicate the command is from kernel modeclient) as part of the source operand for ENQCMDS instruction.

c. Command Payload that is specific to the target device. The commandpayload is read from the source operand and conveyed as is by theinstruction in the non-posted write payload. Depending on the device,the device may use ENQCMD/S in different way. For example, some devicesmay treat it as a doorbell command where the payload specifies theactual work descriptor in memory to fetch from). Other devices may usethe actual ENQ command to carry the device specific work descriptor,thus avoiding the latency/overhead for reading the work descriptors frommain memory.

The SWQ on a device processes a non-posted write request received asfollows:

At the ingress of device SWQ check if there is space in the SWQ toaccept the request. If there is no space, drop the request and return acompletion indicating “Reject/Retry” in completion status.

If there is space to accept command to the SWQ perform any neededdevice-specific admission control based on the attributes in the request(such as PASID, Privilege, or SWQ_PREG address to which the request isrouted) and various device-specific QoS settings for specific clients.If the admission control method determines that the request cannot beaccepted to the SWQ the request is dropped and a completion is returnedwith a completion status of “Reject/Retry”.

If the above checks result in the non-posted write command to beaccepted to the SWQ, a completion is returned with completion status of“Successful Completion”. The command queued to the SWQ isprocessed/dispatched based on the device-specific scheduling modelinternal to the device.

When the work specified by the command is completed, the devicegenerates appropriate synchronization or notification transactions toinform the client about work completions. These could be through memorywrites, interrupt writes, or other methods.

The ENQCMD and ENQCMDS instruction blocks until the completion responseis received back by the CPU. The instruction returns the status (successv/s reject/retry) in the EFLAGS.ZF flag before the instruction retires.

Software may queue work through SWQ as follows:

a. Map the SWQ_PREG of the device to client's CPU virtual address space(user or kernel virtual address, depending of if the client is user-modeor runs in kernel-mode). This is similar to memory-mapping any MMIOresources on a device.

b. Format descriptor in memory

c. Execute ENQCMD/S with the memory virtual address of descriptor assource and the virtual address to which the SWQ_PREG is mapped as thedestination.

d. Execute a condition jump (JZ) to check if the ENQCMD/S instructionreturned success or retry. If retry status, either retry from step-C(with appropriate back

An ENQ non-posted write may be dropped by any agent (uncore, coherentfabric, I/O fabric, bridges, . . . ) between the CPU and the device. Ifany agent drops an ENQ request, such agent must return a completionresponse with retry status code. Software sees and treats it just like aretry response it received from the target SWQ at the device. This ispossible because, ENQ* requests are self-contained and do not have anyordering constraints associated with them. System designs and fabricsmay make use of this property to handle temporal congestion orback-pressure conditions in hardware/fabrics.

This property may also be utilized to build optimized designs where theSWQ may be moved closer to the CPU and use a dedicatedposted/credit-based method to forward accepted commands to the SWQ tothe target device. Such approaches may be useful to improve theround-trip latency of ENQ instruction which otherwise is required tosend the non-posted write request all the way to the SWQ on device andwait for completion.

The SWQ could be implemented on a device by making use of eitherdedicated storage on-chip (SRAM), or using extended memory (DRAM) on thedevice or even reserved/stolen memory in the platform. In these cases,the SWQ is just a front end for the clients to submit work usingnon-posted semantics, and all accepted commands to a SWQ are written toan in-memory work-queue by the device, from which the various executionof the engines can fetch work just like any normal memory-basedwork-queue. Such memory-backed SWQ implementation can allow for a largeSWQ capacity than what may be otherwise possible with dedicated on-chipSRAM storage.

FIG. 5 is a schematic diagram of an example data streaming accelerator(DSA) device comprising multiple work queues that receive descriptorssubmitted over an I/O fabric interface. FIG. 5 illustrates oneimplementation of a data streaming accelerator (DSA) device comprisingmultiple work queues 510-512 which receive descriptors submitted over anI/O fabric interface 504 (e.g., such as the multi-protocol link 314described above). DSA uses the I/O fabric interface 504 for receivingdownstream work requests from clients (such as processor cores, peerinput/output (IO) agents (such as a network interface controller (NIC)),and/or software chained offload requests) and for upstream read, write,and address translation operations. The illustrated implementationincludes an arbiter 514 which arbitrates between the work queues anddispatches a work descriptor to one of a plurality of engines 518. Theoperation of the arbiter 514 and work queues 510-512 may be configuredthrough a work queue configuration register 502. For example, thearbiter 514 may be configured to implement various QoS and/or fairnesspolicies for dispatching descriptors from each of the work queues510-512 to each of the engines 518.

In one implementation, some of the descriptors queued in the work queues510-512 are batch descriptors 520 which contain/identify a batch of workdescriptors. The arbiter 514 forwards batch descriptors to a batchprocessing unit 524 which processes batch descriptors by reading thearray of descriptors 526 from memory, using addresses translated throughtranslation cache 506 (or potentially other address translation serviceson the processor). Once the physical address has been identified dataread/write circuit 508 reads the batch of descriptors from memory.

A second arbiter 528 arbitrates between batches of work descriptors 526provided by the batch processing unit 524 and individual workdescriptors 522 retrieved from the work queues 510-512 and outputs thework descriptors to a work descriptor processing unit 530. In oneimplementation, the work descriptor processing unit 530 has stages toread memory (via data R/W unit 508), perform the requested operation onthe data, generate output data, and write output data (via data R/W unit508), completion records, and interrupt messages.

In one implementation, the work queue configuration allows software toconfigure each WQ (via a WQ configuration register 502) either as aShared Work Queue (SWQ) that receives descriptors using non-postedENQCMD/S instructions or as a Dedicated Work Queue (DWQ) that receivesdescriptors using posted MOVDIR64B instructions. As mentioned above withrespect to FIG. 4, a DWQ may process work descriptors and batchdescriptors submitted from a single application whereas a SWQ may beshared among multiple applications. The WQ configuration register 502also allows software to control which WQs 510-512 feed into whichaccelerator engines 518 and the relative priorities of the WQs 510-512feeding each engine. For example, an ordered set of priorities may bespecified (e.g., high, medium, low; 1, 2, 3, etc.) and descriptors maygenerally be dispatched from higher priority work queues ahead of ormore frequently than dispatches from lower priority work queues. Forexample, with two work queues, identified as high priority and lowpriority, for every 10 descriptors to be dispatched, 8 out of the 10descriptors may be dispatched from the high priority work queue while 2out of the 10 descriptors are dispatched from the low priority workqueue. Various other techniques may be used for achieving differentpriority levels between the work queues 510-512.

In one implementation, the data streaming accelerator (DSA) is softwarecompatible with a PCI Express configuration mechanism and implements aPCI header and extended space in its configuration-mapped register set.The configuration registers can be programmed through CFC/CF8 or MMCFGfrom the Root Complex. All the internal registers may be accessiblethrough the JTAG or SMBus interfaces as well.

In one implementation, the DSA device uses memory-mapped registers forcontrolling its operation. Capability, configuration, and worksubmission registers (portals) are accessible through the MMIO regionsdefined by BAR0, BAR2, and BAR4 registers (described below). Each portalmay be on a separate 4K page so that they may be independently mappedinto different address spaces (clients) using processor page tables.

As mentioned, software specifies work for DSA through descriptors.Descriptors specify the type of operation for DSA to perform, addressesof data and status buffers, immediate operands, completion attributes,etc. (additional details for the descriptor format and details are setforth below). The completion attributes specify the address to which towrite the completion record, and the information needed to generate anoptional completion interrupt.

In one implementation, DSA avoids maintaining client-specific state onthe device. All information to process a descriptor comes in thedescriptor itself. This improves its shareability among user-modeapplications as well as among different virtual machines (or machinecontainers) in a virtualized system.

A descriptor may contain an operation and associated parameters (calleda Work descriptor), or it can contain the address of an array of workdescriptors (called a Batch descriptor). Software prepares thedescriptor in memory and submits the descriptor to a Work Queue (WQ)510-512 of the device. The descriptor is submitted to the device using aMOVDIR64B, ENQCMD, or ENQCMDS instruction depending on WQ's mode andclient's privilege level.

Each WQ 510-512 has a fixed number of slots and hence can become fullunder heavy load. In one implementation, the device provides therequired feedback to help software implement flow control. The devicedispatches descriptors from the work queues 510-512 and submits them tothe engines for further processing. When the engine 518 completes adescriptor or encounters certain faults or errors that result in anabort, it notifies the host software by either writing to a completionrecord in host memory, issuing an interrupt, or both.

In one implementation, each work queue is accessible via multipleregisters, each in a separate 4 KB page in device MMIO space. One worksubmission register for each WQ is called “Non-privileged Portal” and ismapped into user space to be used by user-mode clients. Another worksubmission register is called “Privileged Portal” and is used by thekernel-mode driver. The rest are Guest Portals, and are used bykernel-mode clients in virtual machines.

As mentioned, each work queue 510-512 can be configured to run in one oftwo modes, Dedicated or Shared. DSA exposes capability bits in the WorkQueue Capability register to indicate support for Dedicated and Sharedmodes. It also exposes a control in the Work Queue Configurationregisters 502 to configure each WQto operate in one of the modes. Themode of a WQ can only be changed while the WQ is disabled i.e.,(WQCFG.Enabled=0). Additional details of the WQ Capability Register andthe WQ Configuration Registers are set forth below.

In one implementation, in shared mode, a DSA client uses the ENQCMD orENQCMDS instructions to submit descriptors to the work queue. ENQCMD andENQCMDS use a 64-byte non-posted write and wait for a response from thedevice before completing. The DSA returns a “success” (e.g., to therequesting client/application) if there is space in the work queue, or a“retry” if the work queue is full. The ENQCMD and ENQCMDS instructionsmay return the status of the command submission in a zero flag (0indicates Success, and 1 indicates Retry). Using the ENQCMD and ENQCMDSinstructions, multiple clients can directly and simultaneously submitdescriptors to the same work queue. Since the device provides thisfeedback, the clients can tell whether their descriptors were accepted.

In shared mode, DSA may reserve some SWQ capacity for submissions viathe Privileged Portal for kernel-mode clients. Work submission via theNon-Privileged Portal is accepted until the number of descriptors in theSWQ reaches the threshold configured for the SWQ. Work submission viathe Privileged Portal is accepted until the SWQ is full. Work submissionvia the Guest Portals is limited by the threshold in the same way as theNon-Privileged Portal.

If the ENQCMD or ENQCMDS instruction returns “success,” the descriptorhas been accepted by the device and queued for processing. If theinstruction returns “retry,” software can either try re-submitting thedescriptor to the SWQ, or if it was a user-mode client using theNon-Privileged Portal, it can request the kernel-mode driver to submitthe descriptor on its behalf using the Privileged Portal. This helpsavoid denial of service and provides forward progress guarantees.Alternatively, software may use other methods (e.g., using the CPU toperform the work) if the SWQ is full.

Clients/applications are identified by the device using a 20-bit IDcalled process address space ID (PASID). The PASID is used by the deviceto look up addresses in the Device TLB 1722 and to send addresstranslation or page requests to the IOMMU 1710 (e.g., over themulti-protocol link 2800). In Shared mode, the PASID to be used witheach descriptor is contained in the PASID field of the descriptor. Inone implementation, ENQCMD copies the PASID of the current thread from aparticular register (e.g., PASID MSR) into the descriptor while ENQCMDSallows supervisor mode software to copy the PASID into the descriptor.

Although dedicated mode does not share of a single DWQ by multipleclients/applications, a DSA device can be configured to have multipleDWQs and each of the DWQs can be independently assigned to clients. Inaddition, DWQs can be configured to have the same or different QoSlevels to provided different performance levels for differentclients/applications.

In one implementation, a data streaming accelerator (DSA) contains twoor more engines 518 that process the descriptors submitted to workqueues 510-512. One implementation of the DSA architecture includes 4engines, numbered 0 through 3. Engines 0 and 1 are each able to utilizeup to the full bandwidth of the device (e.g., 30 GB/s for reads and 30GB/s for writes). The combined bandwidth of all engines is also limitedto the maximum bandwidth available to the device.

In one implementation, software configures WQs 510-512 and engines 518into groups using the Group Configuration Registers. Each group containsone or more WQs and one or more engines. The DSA may use any engine in agroup to process a descriptor posted to any WQ in the group and each WQand each engine may be in only one group. The number of groups may bethe same as the number of engines, so each engine can be in a separategroup, but not all groups need to be used if any group contains morethan one engine.

Although the DSA architecture allows great flexibility in configuringwork queues, groups, and engines, the hardware may be narrowly designedfor use in specific configurations. Engines 0 and 1 are may beconfigured in one of two different ways, depending on softwarerequirements. One recommended configuration is to place both engines 0and 1 in the same group. Hardware uses either engine to processdescriptors from any work queue in the group. In this configuration, ifone engine has a stall due to a high-latency memory address translationor page fault, the other engine can continue to operate and maximize thethroughput of the overall device.

FIGS. 6A-B are schematic diagrams illustrating an example DMWr requestscenario in accordance with embodiments of the present disclosure. FIGS.6A-B are schematic diagrams illustrating example DMWr request scenariosin accordance with embodiments of the present disclosure. FIG. 6A showsa system 600 that includes two work queues 610-612 and 614-616 in eachgroup 606 and 608, respectively, but there may be any number up to themaximum number of WQs supported. The WQs in a group may be shared WQswith different priorities, or one shared WQ and the others dedicatedWQs, or multiple dedicated WQs with the same or different priorities. Inthe illustrated example, group 606 is serviced by engines 0 and 1 602and group 608 is serviced by engines 2 and 3 604. Engines 0, 1, 2, and 3can be similar to engine 518.

As illustrated in FIG. 6B, another system 620 using engines 0 622 and 1624 is to place them in separate groups 630 and 632, respectively.Similarly, group 2 634 is assigned to engine 2 626 and group 3 isassigned to engine 3 628. In addition, group 0 630 is comprised of twowork queues 638 and 640; group 1 632 is comprised of work queue 642;work queue 2 634 is comprised of work queue 644; and group 3 636 iscomprised of work queue 646.

Software may choose this configuration when it wants to reduce thelikelihood that latency-sensitive operations become blocked behind otheroperations. In this configuration, software submits latency-sensitiveoperations to the work queue 642 connected to engine 1 626, and otheroperations to the work queues 638-640 connected to engine 0 622.

Engine 2 626 and engine 3 628 may be used, for example, for writing to ahigh bandwidth non-volatile memory such as phase-change memory. Thebandwidth capability of these engines may be sized to match the expectedwrite bandwidth of this type of memory. For this usage, bits 2 and 3 ofthe Engine Configuration register should be set to 1, indicating thatVirtual Channel 1 (VC1) should be used for traffic from these engines.

In a platform with no high bandwidth, non-volatile memory (e.g.,phase-change memory) or when the DSA device is not used to write to thistype of memory, engines 2 and 3 may be unused. However, it is possiblefor software to make use of them as additional low-latency paths,provided that operations submitted are tolerant of the limitedbandwidth.

As each descriptor reaches the head of the work queue, it may be removedby the scheduler/arbiter 514 and forwarded to one of the engines in thegroup. For a Batch descriptor 520, which refers to work descriptors 526in memory, the engine fetches the array of work descriptors from memory(i.e., using batch processing unit 524).

In one implementation, for each work descriptor 522, the engine 518pre-fetches the translation for the completion record address and passesthe operation to the work descriptor processing unit 530. The workdescriptor processing unit 530 uses the Device TLB and IOMMU for sourceand destination address translations, reads source data, performs thespecified operation, and writes the destination data back to memory.When the operation is complete, the engine writes the completion recordto the pre-translated completion address and generates an interrupt, ifrequested by the work descriptor.

In one implementation, DSA's multiple work queues can be used to providemultiple levels of quality of service (QoS). The priority of each WQ maybe specified in the WQ configuration register 502. The priorities of WQsare relative to other WQs in the same group (e.g., there is no meaningto the priority level of a WQ that is in a group by itself). Work queuesin a group may have the same or different priorities. However, there isno point in configuring multiple shared WQs with the same priority inthe same group, since a single SWQ would serve the same purpose. Thescheduler/arbiter 514 dispatches work descriptors from work queues510-512 to the engines 518 according to their priority.

Accelerator devices and high-performance I/O devices support servicingrequests directly from multiple clients. In this context, the termclient (also referred to herein as entities) can include any of thefollowing:

Multiple user-mode (ring 3) applications that are submitting directuser-mode I/O requests to the device;

Multiple kernel-mode (ring 0) drivers running in multiple virtualmachines (VMs) sharing the same device;

Multiple software agents running in multiple containers (with OSsupporting container technologies);

Any combination of above (e.g., ring 3 applications inside a VM,containers hardened by running them in a VM, etc.);

Peer I/O agents submitting work directly for efficient inlineacceleration (e.g., a NIC device using a crypto-device for encryptionacceleration, or a touch controller or image processing unit using theGPU for advanced sensor processing); or

Host software chaining offload requests across accelerators, where anaccelerator device may forward work to another host software specifiedaccelerator to chain work without bouncing through the host (e.g., acompression accelerator compressing first, before chaining work to abulk crypto-accelerator for encryption on the compressed data).

The term “directly” above implies the device is shared with multipleclients without intermediate software layers, such as with common kerneldrivers in case of user applications, or common VMM/hypervisor layers incase of VMs) in the control and data path to minimize software overhead.

Examples of multi-client accelerator/high-performance devices caninclude programmable GPUs, configurable offload devices, reconfigurableoffload devices, fixed-function offload devices, high-performance hostfabric controller devices, or high-performance I/O devices.

Work-submission scalability can be addressed by using the shared workqueues, as described above. This disclosure describes mechanisms toapply shared work queues and achieve work submission scalability usinginterconnect protocols based on the PCIe specification.

This disclosure describes a PCIe packet type, referred to herein as an“Deferred Memory Write Request” (DMWr). In embodiments, the termAcknowledged Memory Write (AMWr) requests is used, and it is understoodthat the concepts are similar. DMWr packets can include the followingfeatures and functions:

DMWr packets are Non-Posted transactions, and as such are handleddifferently than Posted MWr packets by PCIe flow control;

Being Non-Posted transactions, DMWr transactions require a Completion tobe sent back to the Requester; and

Unlike MWr transactions (where the Completer must accept all properlyformatted Requests), DMWr Completers may choose to accept or decline theAMWr Request for any implementation-specific reason.

FIGS. 7A-D are schematic diagrams illustrating an example acknowledgedmemory write (DMWr) request and response message flow in accordance withembodiments of the present disclosure. In general, the I/O device (suchas the accelerator device) supports a common command interface for worksubmissions from its clients. The common command interface can bereferred to as a shared work queue (SWQ). In FIGS. 7A-D, the SWQ isshown as command queue 704. The SWQ can be a command queue 704implemented on the accelerator device. The depth of the command queue704 is implementation-specific and can be sized based on the number ofoutstanding commands required to feed the device to achieve its fullthroughput potential.

An accelerator 702 with a fixed-length FIFO command queue 704 canreceive uncoordinated commands directly from multiple software (orhardware) entities (e.g., entity A and entity B in the examples below).Each entity can issue commands (such as work descriptors) by issuingAMWr Requests to a single fixed memory address. Note that each entitycan issue these commands directly to the device without the need for anysort of coordination mechanism between the other entities issuingcommands.

In the example shown in FIG. 7A, accelerator command queue 704 is nearlyfull. 1) Entity A issues a command to the queue 704 via an DMWr Packet.2) The accelerator can accept the command into the command queue. 3) Theaccelerator 702 can respond with a Successful Completion (SC). Note thatsuch a device may also choose to decline packets before the queue iscompletely full for implementation-specific reasons (e.g., to implementTCP-like flow control mechanism).

In FIG. 7B, the command queue 704 is full. 4) Entity B issues command tothe command queue 704 while the command queue 704 is full. 5) Theaccelerator 702 declines the request, and 6) the accelerator 702 sends aCompletion with Request Retry Status (RRS). 7) If entity B attempts toreissue the command while the queue is still fill, the accelerator 702can continue to send associated Completions with RRS in the statusfield.

In FIG. 7C, 8) the accelerator 702 completes processing a command andspace becomes available on its queue. In FIG. 7D, 9) Entity B (or anyother entity) reissues a command to the accelerator 702. 10) Accelerator702 can now accept the command into command queue 704. 11) Accelerator702 can respond with a Successful Completion (SC) message.

FIG. 8 is a process flow diagram 800 for performing scalable worksubmissions in accordance with embodiments of the present disclosure. Atthe outset, an I/O device, such as an accelerator, can receive from anentity a command into its command queue (802). If the command queue iffull (804), then the accelerator can transmit a Completion with RequestRetry Status (RRS) message to the entity (806). If the command queue isnot full (804), then the accelerator can transmit a SuccessfulCompletion (SC) message to the entity (808) and can accept the commandinto the command for processing (810).

Deferred Memory Write (DMWr):

In some embodiments, a DMWr can be used to send data over PCIe.Deferrable Memory Writes require the Completer to return anacknowledgement to the Requester, and provides a mechanism for therecipient to defer the received data. The DMWr TLP facilitates use-casesthat were previously not possible (or much more difficult to implement)on PCIe-based devices and links. DMWr provides a mechanism for Endpointsand hosts to choose to carry out or defer incoming DMWr Requests. Thismechanism can be used by Endpoints and Hosts to simplify the design offlow control and fixed-length queue mechanisms. With DMWr, devices canhave a single shared work queue and accept work items from multiplenon-cooperating software agents in a non-blocking way. A DMWr can bedefined as a memory write where the Requester attempts to write to agiven location in Memory Space. The Completer can accept or decline thiswrite by returning a completion with status of SC or memory requestretry status (MRS), respectively (similar to the RRS above).

The Deferrable Memory Write (DMWr) is an Optional Non-Posted Requestthat enables a scalable high-performance mechanism to implement sharedwork queues and similar capabilities. With DMWr, devices can have asingle shared work queue and accept work items from multiplenon-cooperating software agents in a non-blocking way.

The following requirements apply to DMWr Completers (a completer can beany entity that completes a non-posted write request transaction):

Completers supporting DMWr Requests handle properly-formatted DMWrRequests as a Successful Completion (SC), Request Retry Status (MRS),Unsupported Request (UR), or Completer Abort (CA) for any location inits target Memory Space.

Completers supporting DMWr handle any properly formed DMWr Requests withtypes or operand sizes they do not support as an Unsupported Request(UR). The value of the target location must remain unchanged.

Completers supporting DMWr are allowed to implement a restrictedprogramming model. Optimizations Based on a Restricted Programming Modelas defined in the PCIe specification.

If any Function in a Multi-Function Device supports DMWr Completer orDMWr routing capability, all Functions with Memory Space BARs in thatdevice must decode properly formed DMWr Requests and handle any they donot support as an Unsupported Request (UR). Note that in such devices,Functions lacking DMWr Completer capability must not handle properlyformed DMWr Requests as Malformed TLPs.

Unless there is a higher precedence error, a DMWr-aware Completer musthandle a Poisoned DMWr Request as a Poisoned TLP Received error, andmust also return a Completion with a Completion Status of UnsupportedRequest (UR). The value of the target location must remain unchanged.

If the Completer of a DMWr Request encounters an uncorrectable erroraccessing the target location, the Completer must handle it as aCompleter Abort (CA). The subsequent state of the target location isimplementation specific.

Completers are permitted to support DMWr Requests on a subset of theirtarget Memory Space as needed by their programming model. Memory Spacestructures defined or inherited by PCI Express (e.g., the MSI-X Tablestructure) are not required to be supported as DMWr targets unlessexplicitly stated in the description of the structure.

If an RC has any Root Ports that support DMWr routing capability, allRCiEPs in the RC reachable by forwarded DMWr Requests must decodeproperly formed DMWr Requests and handle any they do not support as anUnsupported Request (UR).

The following requirements apply to Root Complexes and Switches thatsupport DMWr routing:

If a Switch supports DMWr routing for any of its Ports, the switch doesso for all of them.

For a Switch or an RC, when DMWr Egress Blocking is enabled in an EgressPort and a DMWr Request targets going out that Egress Port, then theEgress Port handles the Request as a DMWr Egress Blocked error and mustalso return a Completion with a Completion Status of UR. If the severityof the DMWr Egress Blocked error is non-fatal, then this case is handledas an Advisory Non-Fatal Error as described in the PCIe specificationgoverning Completers sending a completion with UR/CA status.

For an RC, support for peer-to-peer routing of DMWr Requests andCompletions between Root Ports is optional and implementation dependent.If an RC supports DMWr routing capability between two or more RootPorts, the RC indicates that capability in each associated Root Port viathe DMWr Routing Supported bit in the Device Capabilities 2 register

An RC is not required to support DMWr routing between all pairs of RootPorts that have the DMWr Routing Supported bit Set. Software should notassume that DMWr routing is supported between all pairs of Root Portsthat have the DMWr Routing Supported bit Set.

If an RC supports DMWr routing capability between two or more RootPorts, the RC indicates that capability in each associated Root Port viathe DMWr Routing Supported bit in the Device Capabilities 2 register.

A DMWr Request that is routed through a Root Port that does not supportDMWr is handled as an Unsupported Request (UR).

Implementation Note: Design Considerations for Deferrable Memory Write

In some embodiments, DMWr can be used by devices and device drivers toimplement control mechanisms.

Being a Non-Posted Request, DMWr TLPs use a Completion TLP to finish thetransaction. In addition, PCIe ordering rules dictate that Non-PostedTLPs cannot pass Posted TLPs, making Posted transactions preferable forimproved performance. Because DMWr TLPs cannot pass Memory Read RequestTLPs and DMWr TLPs can be deferred by the Completer, care is to be takenby Device and Device Driver manufacturers when attempting to read amemory location that is also the target of an outstanding DMWrTransaction.

Implementation Note: Ensuring Forward Progress with Deferrable MemoryWrites

When DMWr Transactions are used to create a single shared work queue,care must be taken to ensure that no Requesters are denied accessindefinitely to the queue due to congestion. Software entities thatwrite to such a queue may choose to implement a flow control mechanismor rely on a particular programming model to ensure that all entitiesare able to make forward progress. This programming model may include afeedback mechanism or an indication to from the Function to software onthe state of the queue, or a timer that delays DMWr Requests after aCompletion with status MRS.

Memory Transactions include the following types:

Read Request/Completion;

Write Request;

Deferrable Write Request; and

AtomicOp Request/Completion.

Memory Transactions use two different address formats:

Short Address Format: 32-bit address; and

Long Address Format: 64-bit address.

Certain Memory Transactions can optionally have a PASID TLP Prefixcontaining the Process Address Space ID (PASID).

FIGS. 9A and 9B are visual representations of the AMWr packet. FIG. 9Ais a schematic diagram of a 64-bit DMWr (or AMWr) packet definition 900in accordance with embodiments of the present disclosure. FIG. 9B is aschematic diagram of a 32-bit DMWr (or AMWr) packet definition 920 inaccordance with embodiments of the present disclosure.

Table 2 below represents TLP definitions to support DMWr.

TABLE 2 TLP Definitions to Support DMWr. Fmt Type TLP [2:0] [4:0] Type(b) (b) Description MWr 010 0 0000 Memory Write Request 011 DMWr 010 11011 Deferred Memory Write Request 011 (Deprecated TLP type deleted) . .. . . . . . . . . . Cpl 000 0 1010 Completion without Data - Used forI/O, and Configuration, and Deferrable Memory Write Completions with anyCompletion Status. Also used for AtomicOp Completions and ReadCompletions (I/O, Configuration, or Memory) with Completion Status otherthan Successful Completion.

Table 3 below provides definitions for a completion status.

TABLE 3 Definitions for Completion Status. Completion Status [2:0] FieldValue (b) Completion Status 000 Successful Completion (SC) 001Unsupported Request (UR) 010 Configuration Request Retry Status (CRS)100 Completer Abort (CA) 101 Memory Request Retry Status (MRS) allothers Reserved

Address-based routing rules can also facilitate the DMWr requests.Address routing is used with Memory and I/O Requests. Two addressformats are specified: a 64-bit format used with a 4 DW header and a32-bit format used with a 3 DW header. FIGS. 9A-B represent the 64 and32 bit formats, respectively.

For Memory Read, Memory Write, Deferrable Memory Write, and AtomicOpRequests, the Address Type (AT) field is encoded as shown in Table 10-1Address Type (AT) Field Encodings. For all other Requests, the AT fieldis Reserved unless explicitly stated otherwise. LN Reads and LN Writeshave special requirements.

Memory Read, Memory Write, Deferrable Memory Write, and AtomicOpRequests can use either format.

For Addresses below 4 GB, Requesters must use the 32-bit format. Thebehavior of the Receiver is not specified if a 64-bit format requestaddressing below 4 GB (i.e., with the upper 32 bits of address all 0) isreceived.

I/O Read Requests and I/O Write Requests use the 32-bit format.

Agents decode all address bits in the header-address aliasing is notallowed.

The request handling rules can support DMWr. If the device supportsbeing a target for I/O Write Requests, which are Non-Posted Requests,each associated Completion should be returned within the same time limitas for Posted Request acceptance. If the device supports being a targetfor Deferrable Memory Write Requests, each associated Completion isreturned within the same time limit as for Posted Request acceptance.

Flow control rules can also support DMWr. Each Virtual Channel hasindependent Flow Control. Flow Control distinguishes three types ofTLPs:

Posted Requests (P)—Messages and Memory Writes;

Non-Posted Requests (NP)—All Reads, I/O Writes, Configuration Writes,AtomicOps, and Deferrable Memory Writes; and

Completions (Cpl)—Associated with corresponding NP Requests

In addition, Flow Control distinguishes the following types of TLPinformation within each of the three types: Headers (H); and Data (D).

Thus, there are six types of information tracked by Flow Control foreach Virtual Channel, as shown in Table 4 Flow Control Credit Types.

TABLE 4 Flow Control Credit Types. Credit Type Completion Status PHPosted Request Header PD Posted Request Data Payload NPH Non-PostedRequest Header NPD Non-Posted Request Data Payload CplH CompletionHeaders CplD Completion Data Payload

TLPs consume Flow Control credits as shown in Table 5 TLP Flow ControlCredit Consumption.

TABLE 5 TLP Flow Control Credit Consumption. TLP Credit Consumed Memory,I/O, Configuration Read Request 1 NPH unit Memory Write Request 1 PH + nPD units I/O, Configuration Write Request 1 NPH + 1 NPD Note: size ofdata written is never more than 1 (aligned) DW AtomicOp, DeferrableMemory Write 1 NPH + n NPD units Request Message Requests without data 1PH unit Message Requests with data 1 PH + n NPD units Memory ReadCompletion 1 CplH + n CplD units I/O, Configuration Read Completions 1CplH unit + 1 CplH unit I/O, Configuration, Deferrable Memory 1 CplHunit Write Completions AtomicOp Completion 1 CplH unit + 1 CplD unitNote: size of data returned is never more than 4 (aligned) DWs

Table 6 shows minimum advertisement for the NPD credit type.

TABLE 6 Minimum Initial Flow Control Advertisements. MinimumAdvertisement Credit Type No Scaling or Scale Factor 1 Scale Factor 4Scale Factor 16 . . . . . . . . . . . . NPD Receiver that supportsReceiver that supports Receiver that DMWr routing capability or DMWrrouting capability or supports DMWr DMWr Completer DMWr Completerrouting capability or capability: 4 units - credit capability: 4 units -credit DMWr Completer value of 004h value of 004h capability: 4 units -Receiver that supports Receiver that supports credit value of 004hAtomicOp routing AtomicOp routing Receiver that capability or anyAtomicOp capability or any AtomicOp supports AtomicOp Completercapability: 2 Completer capability: 2 routing capability or units -credit value of 002h units - credit value of 002h any AtomicOp All otherReceivers: 1 unit - All other Receivers: 1 unit - Completer credit valueof 001h. credit value of 001h. capability: 2 units - credit value of002h All other Receivers: 1 unit - credit value of 001h. . . . . . . . .. . . .

For errors detected in the Transaction layer and Uncorrectable InternalErrors, it is permitted and recommended that no more than one error bereported for a single received TLP, and that the following precedence(from highest to lowest) be used:

Uncorrectable Internal Error

Receiver Overflow;

Malformed TLP;

ECRC Check Failed;

AtomicOp or DMWr Egress Blocked;

TLP Prefix Blocked;

ACS Violation;

MC Blocked TLP;

Unsupported Request (UR), Completer Abort (CA), or UnexpectedCompletion; and

Poisoned TLP Received or Poisoned TLP Egress Blocked

Table 7 shows a transaction layer error list. The transaction layererror list can be used by detecting agents, such as egress ports, toidentify errors when handling DMWr packets.

TABLE 7 Transaction Layer Error List. Error Type Detecting Agent ActionError (Default [4:0] Name Severity) (b) References . . . . . . . . . . .. AtomicOP . . . . . . . . . Egress Blockedr DMWr Uncorrectable EgressPort: Section re: Deferred Memory Egress (non-fatal) Send ERR_COR toRoot Write Blocked Complex. This is an Advisory Non-Fatal Error casedescribed in Section 6.2.3.2.4.1 Completer Sending a Completion withUR/CA Status. Log the prefix/header of the DMWr Request that encounteredthe error. . . . . . . . . . . . .

Table 8 provides bit mapping to a device capabilities 2 register:

TABLE 8 Device Capabilities 2 Register. Bit Location RegisterDescription Attributes . . . . . . . . . 27 DMWr Routing Supported -Applicable only to HWInit Switch Upstream Ports, Switch DownstreamPorts, and Root Ports; must be 0 b for other Function types. This bitmust be set to 1 b if the Port supports this optional capability. 28DMWr Completer Supported - Applicable to HWInit Functions with MemorySpace BARs as well as all Root Ports; This bit must be set to 1 b if thefunction can serve as a DMWr Completer. . . . . . . . . .

Table 9 provides bit mapping to a device capabilities 4 register:

TABLE 9 Device Capabilities 3 Register. Bit Location RegisterDescription Attributes 0 Deferrable Memory Write Requester Enable -Applicable only to RW Endpoints and Root Ports; must be hardwired to 0 bfor other Function types. The Function is allowed to initiate DeferrableMemory Writes only if this bit and the Bus Master Enable bit in theCommand register are both Set. This bit is required to be RW if theEndpoint or Root Port is capable of initiating Deferrable Memory WriteRequests, but otherwise is permitted to be hardwired to 0 b. Defaultvalue of this bit is 0 b. 28 Deferrable Memory Write Egress Blocking -Applicable and RW mandatory for Switch Upstream Ports, Switch DownstreamPorts, and Root Ports that implement Deferrable Memory Write routing;otherwise must be hardwired to 0 b. When this bit is Set, DeferrableMemory Write Requests that target going out this Egress Port must beblocked. See Section 6.30 Default value of this bit is 0 b.

Table 10 represents definitions to uncorrectable error status registerbit values.

TABLE 10 Uncorrectable Error Status Register. Bit Location RegisterDescription Attributes Default . . . . . . . . . . . . 1 DMWr EgressBlocked Status RW1CS 0 b . . . . . . . . . . . .

Table 11 represents definitions of uncorrectable error mask register bitvalues.

TABLE 11 Uncorrectable Error Mask Register. Bit Location RegisterDescription Attributes Default . . . . . . . . . . . . 1 DMWr EgressBlocked RWS 0 b Mask (Optional) . . . . . . . . . . . .

Table 12 represents definitions of uncorrectable error severity registerbit values.

TABLE 12 Uncorrectable Error Severity Register. Bit Location RegisterDescription Attributes Default . . . . . . . . . . . . 1 DMWr EgressBlocked Severity RWS 0 b (Optional) . . . . . . . . . . . .

In embodiments, AMWr can be used for non-posted write requests forscability of work requests to completers. The following features canfacilitate AMWr messaging on PCIe based interconnects:

The definition of a Transaction Layer Packet (TLP) Type “AMWr” (e.g.,using value 0b11011, which was previously used for the deprecated TCfgWrTLP Type);

The expansion of the CRS Completion Status to be applicable to othernon-configuration Packets (referred to herein as “Request Retry Status(RRS)”;

Adding AMWr Routing and Egress Blocking support to PCIe Ports;

Adding AMWr Requester & Completer Support to Endpoints and RootComplexes; and

Adding AMWr Egress Blocked reporting to Advanced Error Reporting (AER).

The Acknowledged Memory Write (AMWr) is a Non-Posted Request and enableseasy scalability for high performance, low latency devices such asaccelerators, implementing a shared work queue or an acknowledgeddoorbell write. The number of unique application clients that can submitwork to such devices is typically dependent on the number of queues anddoorbells supported by the device. With AMWr, accelerator-type (andother I/O) devices can have a single shared work queue and accept workitems from multiple non-cooperating software agents in a non-blockingway. Devices could expose such shared work queues in animplementation-specific way.

As with other PCIe Transactions, the support for peer-to-peer routing ofAMWr Requests and Completions between Root Ports is optional andimplementation dependent. If a Root Complex (RC) supports AMWr routingcapability between two or more Root Ports, the RC indicates thatcapability in each associated Root Port via the AMWr Routing Supportedbit in the Device Capabilities 2 register

If a Switch supports AMWr routing for any of its Ports, it may do so forall of them.

For a Switch or an RC, when AMWr Egress Blocking is enabled in an EgressPort, and an AMWr Request targets going out from that Egress Port, theEgress Port handles the Request as an Unsupported Request error and mustalso return a Completion with a Completion Status of UR.

In embodiments, for a Switch or an RC, when AMWr Egress Blocking isenabled in an Egress Port, and an AMWr Request targets going out fromthat Egress Port, the Egress Port handles the Request as an AMWr EgressBlocked error and also returns a Completion with a Completion Status ofUR. If the severity of the AMWr Egress Blocked error is non-fatal, thiscase must be handled as an Advisory Non-Fatal Error.

An RC is not required to support AMWr routing between all pairs of RootPorts that have the AMWr Routing Supported bit Set. An AMWr Request thatwould require routing between unsupported pairs of Root Ports must behandled as an Unsupported Request (UR), and reported by the “sending”Port. If a RC supports AMWr routing capability between two or more RootPorts, it must indicate that capability in each associated Root Port viathe AW Routing Supported bit in the Device Capabilities 2 register.Software must not assume that AMWr routing is supported between allpairs of Root Ports that have the AMWr Routing Supported bit Set.

Completers (e.g., entities completing the AMWr requests) supporting AMWrRequests are required to handle properly formatted AMWr Requests as aSuccessful Completion (SC), Request Retry Status (RRS), UnsupportedRequest (UR), or Completer Abort (CA) for any location in its targetMemory Space. The following features apply to AMWr Completers:

Unless there is a higher precedence error, an AMWr-aware Completerhandles a poisoned or corrupted AMWr Request as a Poisoned TLP Receivederror and returns a Completion with a Completion Status of UnsupportedRequest (UR). The value of the target location must remain unchanged.

If the Completer of an AMWr Request encounters an uncorrectable erroraccessing the target location or carrying out the Acknowledged Write,the Completer must handle it as a Completer Abort (CA). The subsequentstate of the target location is implementation specific.

AMWr-aware Completers are required to handle any properly formed AMWrRequests with types or operand sizes they do not support as anUnsupported Request (UR).

If any Function in a Multi-Function Device supports AMWr Completer orAMWr routing capability, all Functions with Memory Space BARs in thatdevice can decode properly formed AMWr Requests and handle any supportedfunctions as an Unsupported Request (UR). Note that in such devices,Functions lacking AMWr Completer capability are forbidden to handleproperly formed AMWr Requests as Malformed TLPs.

If an RC has any Root Ports that support AMWr routing capability, allRCiEPs in the RC reachable by forwarded AMWr Requests must decodeproperly formed AMWr Requests and handle any they do not support as anUnsupported Request (UR).

With an AMWr Request having a supported type and operand size, theAMWr-aware Completer is required either to carry out the Request orhandle it as Completer Abort (CA) for any location in its target MemorySpace. Completers are permitted to support AMWr Requests on a subset oftheir target Memory Space as needed by their programming model (seeSection 2.3.1 Request Handling Rules). Memory Space structures definedor inherited by PCI Express (e.g., the MSI-X Table structure) are notrequired to be supported as AMWr targets unless explicitly stated in thedescription of the structure.

Implementing AMWr Completer support is optional.

In some embodiments, AMWr can be used by devices and device drivers toimplement control mechanisms.

Being a Non-Posted Request, AMWr TLPs uses a Completion TLP to finishthe transaction. In addition, PCIe ordering rules state that Non-PostedTLPs cannot pass Posted TLPs, making Posted transactions preferable forimproved performance.

The packet definitions can be interpreted based, at least in part, onthe following definitions, which can represent changes to the PCIespecification:

Memory Transactions include the following types:

Read Request/Completion;

Write Request;

Acknowledged Write Request (adding the AMWr packet here);

AtomicOp Request/Completion; etc.

Table 13 below is a representation of Table 2-3 of the PCIespecification. Here, the Table 13 includes TLP definitions to supportAMWr.

TABLE 13 TLP Definitions to Support AMWr. Fmt Type [2:0] [4:0] TLP Type(b) (b) Description . . . . . . . . . . . . AMWr 010 11011 AcknowledgedMemory Write Request 011 . . . . . . . . . . . . Cpl 000 01010Completion without Data - Used for I/O, Configuration, and AcknowledgedMemory Write Completions with any Completion Status. Also used forAtomicOp Completions and Read Completions (I/O, Configuration, orMemory) with Completion Status other than Successful Completion.

Table 14 below provides definitions for a completion status.

TABLE 14 Definitions for Completion Status. Completion Status [2:0]Field Value (b) Completion Status 000 Successful Completion (SC) 001Unsupported Request (UR) 010 Request Retry Status (RRS) 100 CompleterAbort (CA) all others Reserved

Various other changes to the PCIe specification can be made tofacilitate the AMWr messaging for scalable workflow submissions.

The following register and bit values can be defined to support AMWr:

In a device control 3 register (e.g., as defined in PCIe specification),Table 15 can provide a definition or register bits.

TABLE 15 Device Control 3 Register. Bit Location Register DescriptionAttributes 0 Acknowledged Memory Write Requester Enable - RW Applicableonly to Endpoints and Root Ports; must be hardwired to 0 b for otherFunction types. The Function is allowed to initiate Acknowledged MemoryWrites only if this bit and the Bus Master Enable bit in the Commandregister are both Set. This bit is required to be RW if the Endpoint orRoot Port is capable of initiating Acknowledged Memory Write Requests,but otherwise is permitted to be hardwired to 0 b. Default value of thisbit is 0 b. 1 Acknowledged Memory Write Egress Blocking - RW Applicableand mandatory for Switch Upstream Ports, Switch Downstream Ports, andRoot Ports that implement Acknowledged Memory Write routing; otherwisemust be hardwired to 0 b. When this bit is Set, Acknowledged MemoryWrite Requests that target going out this Egress Port must be blocked.Default value of this bit is 0 b.

Table 16 represents definitions of uncorrectable error status registerbit values.

TABLE 16 Uncorrectable Error Status Register. Bit Location RegisterDescription Attributes Default . . . . . . . . . . . . 1 AMWr EgressBlocked RW1CS 0 b Status (Optional) . . . . . . . . . . . .

Table 17 represents definitions of uncorrectable error mask register bitvalues.

TABLE 17 Uncorrectable Error Mask Register. Bit Location RegisterDescription Attributes Default . . . . . . . . . . . . 1 AMWr EgressBlocked RWS 0 b Mask (Optional) . . . . . . . . . . . .

Table 18 represents definitions of uncorrectable error severity registerbit values.

TABLE 18 Uncorrectable Error Severity Register. Bit Location RegisterDescription Attributes Default . . . . . . . . . . . . 1 AMWr EgressBlocked RWS 0 b Severity (Optional) . . . . . . . . . . . .

FIG. 10 illustrates an embodiment of a computing system including aninterconnect architecture. Referring to FIG. 10, an embodiment of afabric composed of point-to-point Links that interconnect a set ofcomponents is illustrated. System 1000 includes processor 1005 andsystem memory 1010 coupled to controller hub 1015. Processor 1005includes any processing element, such as a microprocessor, a hostprocessor, an embedded processor, a co-processor, or other processor.Processor 1005 is coupled to controller hub 1015 through front-side bus(FSB) 1006. In one embodiment, FSB 1006 is a serial point-to-pointinterconnect as described below. In another embodiment, link 1006includes a serial, differential interconnect architecture that iscompliant with different interconnect standard.

System memory 1010 includes any memory device, such as random accessmemory (RAM), non-volatile (NV) memory, or other memory accessible bydevices in system 1000. System memory 1010 is coupled to controller hub1015 through memory interface 1016. Examples of a memory interfaceinclude a double-data rate (DDR) memory interface, a dual-channel DDRmemory interface, and a dynamic RAM (DRAM) memory interface.

In one embodiment, controller hub 1015 is a root hub, root complex, orroot controller in a Peripheral Component Interconnect Express (PCIe orPCIE) interconnection hierarchy. Examples of controller hub 1015 includea chipset, a memory controller hub (MCH), a northbridge, an interconnectcontroller hub (ICH) a southbridge, and a root controller/hub. Often theterm chipset refers to two physically separate controller hubs, i.e. amemory controller hub (MCH) coupled to an interconnect controller hub(ICH). Note that current systems often include the MCH integrated withprocessor 1005, while controller 1015 is to communicate with I/Odevices, in a similar manner as described below. In some embodiments,peer-to-peer routing is optionally supported through root complex 1015.

Here, controller hub 1015 is coupled to switch/bridge 1020 throughserial link 1019. Input/output modules 1017 and 1021, which may also bereferred to as interfaces/ports 1017 and 1021, include/implement alayered protocol stack to provide communication between controller hub1015 and switch 1020. In one embodiment, multiple devices are capable ofbeing coupled to switch 1020.

Switch/bridge 1020 routes packets/messages from device 1025 upstream,i.e. up a hierarchy towards a root complex, to controller hub 1015 anddownstream, i.e. down a hierarchy away from a root controller, fromprocessor 1005 or system memory 1010 to device 1025. Switch 1020, in oneembodiment, is referred to as a logical assembly of multiple virtualPCI-to-PCI bridge devices. Device 1025 includes any internal or externaldevice or component to be coupled to an electronic system, such as anI/O device, a Network Interface Controller (NIC), an add-in card, anaudio processor, a network processor, a hard-drive, a storage device, aCD/DVD ROM, a monitor, a printer, a mouse, a keyboard, a router, aportable storage device, a Firewire device, a Universal Serial Bus (USB)device, a scanner, and other input/output devices. Often in the PCIevernacular, such as device, is referred to as an endpoint. Although notspecifically shown, device 1025 may include a PCIe to PCI/PCI-X bridgeto support legacy or other version PCI devices. Endpoint devices in PCIeare often classified as legacy, PCIe, or root complex integratedendpoints.

Graphics accelerator 1030 is also coupled to controller hub 1015 throughserial link 1032. In one embodiment, graphics accelerator 1030 iscoupled to an MCH, which is coupled to an ICH. Switch 1020, andaccordingly I/O device 1025, is then coupled to the ICH. I/O modules1031 and 1018 are also to implement a layered protocol stack tocommunicate between graphics accelerator 1030 and controller hub 1015.Similar to the MCH discussion above, a graphics controller or thegraphics accelerator 1030 itself may be integrated in processor 1005.

FIG. 11 illustrates an embodiment of a interconnect architectureincluding a layered stack. Turning to FIG. 11 an embodiment of a layeredprotocol stack is illustrated. Layered protocol stack 1100 includes anyform of a layered communication stack, such as a Quick Path Interconnect(QPI) stack, a PCie stack, a next generation high performance computinginterconnect stack, or other layered stack. Although the discussionimmediately below in reference to FIGS. 10-13 are in relation to a PCIestack, the same concepts may be applied to other interconnect stacks. Inone embodiment, protocol stack 1100 is a PCIe protocol stack includingtransaction layer 1105, link layer 1110, and physical layer 1120. Aninterface, such as interfaces 1017, 1018, 1021, 1022, 1026, and 1031 inFIG. 1, may be represented as communication protocol stack 1100.Representation as a communication protocol stack may also be referred toas a module or interface implementing/including a protocol stack.

PCI Express uses packets to communicate information between components.Packets are formed in the Transaction Layer 1105 and Data Link Layer1110 to carry the information from the transmitting component to thereceiving component. As the transmitted packets flow through the otherlayers, they are extended with additional information necessary tohandle packets at those layers. At the receiving side the reverseprocess occurs and packets get transformed from their Physical Layer1120 representation to the Data Link Layer 1110 representation andfinally (for Transaction Layer Packets) to the form that can beprocessed by the Transaction Layer 1105 of the receiving device.

Transaction Layer

In one embodiment, transaction layer 1105 is to provide an interfacebetween a device's processing core and the interconnect architecture,such as data link layer 1110 and physical layer 1120. In this regard, aprimary responsibility of the transaction layer 1105 is the assembly anddisassembly of packets (i.e., transaction layer packets, or TLPs). Thetranslation layer 1105 typically manages credit-base flow control forTLPs. PCIe implements split transactions, i.e. transactions with requestand response separated by time, allowing a link to carry other trafficwhile the target device gathers data for the response.

In addition PCIe utilizes credit-based flow control. In this scheme, adevice advertises an initial amount of credit for each of the receivebuffers in Transaction Layer 1105. An external device at the oppositeend of the link, such as controller hub 115 in FIG. 1, counts the numberof credits consumed by each TLP. A transaction may be transmitted if thetransaction does not exceed a credit limit. Upon receiving a response anamount of credit is restored. An advantage of a credit scheme is thatthe latency of credit return does not affect performance, provided thatthe credit limit is not encountered.

In one embodiment, four transaction address spaces include aconfiguration address space, a memory address space, an input/outputaddress space, and a message address space. Memory space transactionsinclude one or more of read requests and write requests to transfer datato/from a memory-mapped location. In one embodiment, memory spacetransactions are capable of using two different address formats, e.g., ashort address format, such as a 32-bit address, or a long addressformat, such as 64-bit address. Configuration space transactions areused to access configuration space of the PCIe devices. Transactions tothe configuration space include read requests and write requests.Message space transactions (or, simply messages) are defined to supportin-band communication between PCIe agents.

Therefore, in one embodiment, transaction layer 1105 assembles packetheader/payload 1106. Format for current packet headers/payloads may befound in the PCIe specification at the PCIe specification website.

Quickly referring to FIG. 12: FIG. 12 illustrates an embodiment of arequest or packet to be generated or received within an interconnectarchitecture. An embodiment of a PCIe transaction descriptor isillustrated. In one embodiment, transaction descriptor 1200 is amechanism for carrying transaction information. In this regard,transaction descriptor 1200 supports identification of transactions in asystem. Other potential uses include tracking modifications of defaulttransaction ordering and association of transaction with channels.

Transaction descriptor 1200 includes global identifier field 1202,attributes field 1204 and channel identifier field 1206. In theillustrated example, global identifier field 1202 is depicted comprisinglocal transaction identifier field 1208 and source identifier field1210. In one embodiment, global transaction identifier 1202 is uniquefor all outstanding requests.

According to one implementation, local transaction identifier field 1208is a field generated by a requesting agent, and it is unique for alloutstanding requests that require a completion for that requestingagent. Furthermore, in this example, source identifier 1210 uniquelyidentifies the requestor agent within a PCIe hierarchy. Accordingly,together with source ID 1210, local transaction identifier 1208 fieldprovides global identification of a transaction within a hierarchydomain.

Attributes field 1204 specifies characteristics and relationships of thetransaction. In this regard, attributes field 1204 is potentially usedto provide additional information that allows modification of thedefault handling of transactions. In one embodiment, attributes field1204 includes priority field 1212, reserved field 1214, ordering field1216, and no-snoop field 1218. Here, priority sub-field 1212 may bemodified by an initiator to assign a priority to the transaction.Reserved attribute field 1214 is left reserved for future, orvendor-defined usage. Possible usage models using priority or securityattributes may be implemented using the reserved attribute field.

In this example, ordering attribute field 1216 is used to supplyoptional information conveying the type of ordering that may modifydefault ordering rules. According to one example implementation, anordering attribute of “0” denotes default ordering rules are to apply,wherein an ordering attribute of “1” denotes relaxed ordering, whereinwrites can pass writes in the same direction, and read completions canpass writes in the same direction. Snoop attribute field 1218 isutilized to determine if transactions are snooped. As shown, channel IDField 1206 identifies a channel that a transaction is associated with.

Link Layer

Link layer 1110, also referred to as data link layer 1110, acts as anintermediate stage between transaction layer 1105 and the physical layer1120. In one embodiment, a responsibility of the data link layer 1110 isproviding a reliable mechanism for exchanging Transaction Layer Packets(TLPs) between two components a link. One side of the Data Link Layer1110 accepts TLPs assembled by the Transaction Layer 1105, appliespacket sequence identifier 1111, i.e. an identification number or packetnumber, calculates and applies an error detection code, i.e. CRC 1112,and submits the modified TLPs to the Physical Layer 1120 fortransmission across a physical to an external device.

Physical Layer

In one embodiment, physical layer 1120 includes logical sub block 1121and electrical sub-block 1122 to physically transmit a packet to anexternal device. Here, logical sub-block 1121 is responsible for the“digital” functions of Physical Layer 1121. In this regard, the logicalsub-block includes a transmit section to prepare outgoing informationfor transmission by physical sub-block 1122, and a receiver section toidentify and prepare received information before passing it to the LinkLayer 1110.

Physical block 1122 includes a transmitter and a receiver. Thetransmitter is supplied by logical sub-block 1121 with symbols, whichthe transmitter serializes and transmits onto to an external device. Thereceiver is supplied with serialized symbols from an external device andtransforms the received signals into a bit-stream. The bit-stream isde-serialized and supplied to logical sub-block 1121. In one embodiment,an 8b/10b transmission code is employed, where ten-bit symbols aretransmitted/received. Here, special symbols are used to frame a packetwith frames 1123. In addition, in one example, the receiver alsoprovides a symbol clock recovered from the incoming serial stream.

As stated above, although transaction layer 1105, link layer 1110, andphysical layer 1120 are discussed in reference to a specific embodimentof a PCIe protocol stack, a layered protocol stack is not so limited. Infact, any layered protocol may be included/implemented. As an example,an port/interface that is represented as a layered protocol includes:(1) a first layer to assemble packets, i.e. a transaction layer; asecond layer to sequence packets, i.e. a link layer; and a third layerto transmit the packets, i.e. a physical layer. As a specific example, acommon standard interface (CSI) layered protocol is utilized.

FIG. 13 illustrates an embodiment of a transmitter and receiver pair foran interconnect architecture. An embodiment of a PCIe serial point topoint fabric is illustrated. Although an embodiment of a PCIe serialpoint-to-point link is illustrated, a serial point-to-point link is notso limited, as it includes any transmission path for transmitting serialdata. In the embodiment shown, a basic PCIe link includes two,low-voltage, differentially driven signal pairs: a transmit pair1306/1311 and a receive pair 1312/1307. Accordingly, device 1305includes transmission logic 1306 to transmit data to device 1310 andreceiving logic 1307 to receive data from device 1310. In other words,two transmitting paths, i.e. paths 1316 and 1317, and two receivingpaths, i.e. paths 1318 and 1319, are included in a PCIe link.

A transmission path refers to any path for transmitting data, such as atransmission line, a copper line, an optical line, a wirelesscommunication channel, an infrared communication link, or othercommunication path. A connection between two devices, such as device1305 and device 1310, is referred to as a link, such as link 1315. Alink may support one lane—each lane representing a set of differentialsignal pairs (one pair for transmission, one pair for reception). Toscale bandwidth, a link may aggregate multiple lanes denoted by xN,where N is any supported Link width, such as 1, 2, 4, 8, 12, 16, 32, 64,or wider.

A differential pair refers to two transmission paths, such as lines 1316and 1317, to transmit differential signals. As an example, when line1316 toggles from a low voltage level to a high voltage level, i.e. arising edge, line 1317 drives from a high logic level to a low logiclevel, i.e. a falling edge. Differential signals potentially demonstratebetter electrical characteristics, such as better signal integrity, i.e.cross-coupling, voltage overshoot/undershoot, ringing, etc. This allowsfor better timing window, which enables faster transmission frequencies.

FIG. 14 illustrates another embodiment of a block diagram for acomputing system including a processor. Turning to FIG. 14, a blockdiagram of an exemplary computer system formed with a processor thatincludes execution units to execute an instruction, where one or more ofthe interconnects implement one or more features in accordance with oneembodiment of the present invention is illustrated. System 1400 includesa component, such as a processor 1402 to employ execution unitsincluding logic to perform algorithms for process data, in accordancewith the present invention, such as in the embodiment described herein.System 1400 is representative of processing systems based on the PENTIUMIII™, PENTIUM 4™, Xeon™, Itanium, XScale™ and/or StrongARM™microprocessors available from Intel Corporation of Santa Clara, Calif.,although other systems (including PCs having other microprocessors,engineering workstations, set-top boxes and the like) may also be used.In one embodiment, sample system 1400 executes a version of the WINDOWS™operating system available from Microsoft Corporation of Redmond, Wash.,although other operating systems (UNIX and Linux for example), embeddedsoftware, and/or graphical user interfaces, may also be used. Thus,embodiments of the present invention are not limited to any specificcombination of hardware circuitry and software.

Embodiments are not limited to computer systems. Alternative embodimentsof the present invention can be used in other devices such as handhelddevices and embedded applications. Some examples of handheld devicesinclude cellular phones, Internet Protocol devices, digital cameras,personal digital assistants (PDAs), and handheld PCs. Embeddedapplications can include a micro controller, a digital signal processor(DSP), system on a chip, network computers (NetPC), set-top boxes,network hubs, wide area network (WAN) switches, or any other system thatcan perform one or more instructions in accordance with at least oneembodiment.

In this illustrated embodiment, processor 1402 includes one or moreexecution units 1408 to implement an algorithm that is to perform atleast one instruction. One embodiment may be described in the context ofa single processor desktop or server system, but alternative embodimentsmay be included in a multiprocessor system. System 1400 is an example ofa ‘hub’ system architecture. The computer system 1400 includes aprocessor 1402 to process data signals. The processor 1402, as oneillustrative example, includes a complex instruction set computer (CISC)microprocessor, a reduced instruction set computing (RISC)microprocessor, a very long instruction word (VLIW) microprocessor, aprocessor implementing a combination of instruction sets, or any otherprocessor device, such as a digital signal processor, for example. Theprocessor 1402 is coupled to a processor bus 1410 that transmits datasignals between the processor 1402 and other components in the system1400. The elements of system 1400 (e.g. graphics accelerator 1412,memory controller hub 1416, memory 1420, I/O controller hub 1424,wireless transceiver 1426, Flash BIOS 1428, Network controller 1434,Audio controller 1436, Serial expansion port 1438, I/O controller 1440,etc.) perform their conventional functions that are well known to thosefamiliar with the art.

In one embodiment, the processor 1402 includes a Level 1 (L1) internalcache memory 1404. Depending on the architecture, the processor 1402 mayhave a single internal cache or multiple levels of internal caches.Other embodiments include a combination of both internal and externalcaches depending on the particular implementation and needs. Registerfile 1406 is to store different types of data in various registersincluding integer registers, floating point registers, vector registers,banked registers, shadow registers, checkpoint registers, statusregisters, and instruction pointer register.

Execution unit 1408, including logic to perform integer and floatingpoint operations, also resides in the processor 1402. The processor1402, in one embodiment, includes a microcode (ucode) ROM to storemicrocode, which when executed, is to perform algorithms for certainmacroinstructions or handle complex scenarios. Here, microcode ispotentially updateable to handle logic bugs/fixes for processor 1402.For one embodiment, execution unit 1408 includes logic to handle apacked instruction set 1409. By including the packed instruction set1409 in the instruction set of a general-purpose processor 1402, alongwith associated circuitry to execute the instructions, the operationsused by many multimedia applications may be performed using packed datain a general-purpose processor 1402. Thus, many multimedia applicationsare accelerated and executed more efficiently by using the full width ofa processor's data bus for performing operations on packed data. Thispotentially eliminates the need to transfer smaller units of data acrossthe processor's data bus to perform one or more operations, one dataelement at a time.

Alternate embodiments of an execution unit 1408 may also be used inmicro controllers, embedded processors, graphics devices, DSPs, andother types of logic circuits. System 1400 includes a memory 1420.Memory 1420 includes a dynamic random access memory (DRAM) device, astatic random access memory (SRAM) device, flash memory device, or othermemory device. Memory 1420 stores instructions and/or data representedby data signals that are to be executed by the processor 1402.

Note that any of the aforementioned features or aspects of the inventionmay be utilized on one or more interconnect illustrated in FIG. 14. Forexample, an on-die interconnect (ODI), which is not shown, for couplinginternal units of processor 1402 implements one or more aspects of theinvention described above. Or the invention is associated with aprocessor bus 1410 (e.g. Intel Quick Path Interconnect (QPI) or otherknown high performance computing interconnect), a high bandwidth memorypath 1418 to memory 1420, a point-to-point link to graphics accelerator1412 (e.g. a Peripheral Component Interconnect express (PCIe) compliantfabric), a controller hub interconnect 1422, an I/O or otherinterconnect (e.g. USB, PCI, PCIe) for coupling the other illustratedcomponents. Some examples of such components include the audiocontroller 1436, firmware hub (flash BIOS) 1428, wireless transceiver1426, data storage 1424, legacy I/O controller 1410 containing userinput and keyboard interfaces 1442, a serial expansion port 1438 such asUniversal Serial Bus (USB), and a network controller 1434. The datastorage device 1424 can comprise a hard disk drive, a floppy disk drive,a CD-ROM device, a flash memory device, or other mass storage device.

FIG. 15 illustrates another embodiment of a block diagram for acomputing system. Turning next to FIG. 15, an embodiment of a systemon-chip (SOC) design in accordance with the inventions is depicted. As aspecific illustrative example, SOC 1500 is included in user equipment(UE). In one embodiment, UE refers to any device to be used by anend-user to communicate, such as a hand-held phone, smartphone, tablet,ultra-thin notebook, notebook with broadband adapter, or any othersimilar communication device. Often a UE connects to a base station ornode, which potentially corresponds in nature to a mobile station (MS)in a GSM network.

Here, SOC 1500 includes 2 cores-1506 and 1507. Similar to the discussionabove, cores 1506 and 1507 may conform to an Instruction SetArchitecture, such as an Intel® Architecture Core™-based processor, anAdvanced Micro Devices, Inc. (AMD) processor, a MIPS-based processor, anARM-based processor design, or a customer thereof, as well as theirlicensees or adopters. Cores 1506 and 1507 are coupled to cache control1508 that is associated with bus interface unit 1509 and L2 cache 1510to communicate with other parts of system 1500. Interconnect 1510includes an on-chip interconnect, such as an IOSF, AMBA, or otherinterconnect discussed above, which potentially implements one or moreaspects of the described invention.

Interface 1510 provides communication channels to the other components,such as a Subscriber Identity Module (SIM) 1530 to interface with a SIMcard, a boot rom 1535 to hold boot code for execution by cores 1506 and1507 to initialize and boot SOC 1500, a SDRAM controller 1540 tointerface with external memory (e.g. DRAM 1560), a flash controller 1545to interface with non-volatile memory (e.g. Flash 1565), a peripheralcontrol Q1650 (e.g. Serial Peripheral Interface) to interface withperipherals, video codecs 1520 and Video interface 1525 to display andreceive input (e.g. touch enabled input), GPU 1515 to perform graphicsrelated computations, etc. Any of these interfaces may incorporateaspects of the invention described herein.

In addition, the system illustrates peripherals for communication, suchas a Bluetooth module 1570, 3G modem 1575, GPS 1585, and WiFi 1585. Noteas stated above, a UE includes a radio for communication. As a result,these peripheral communication modules are not all required. However, ina UE some form a radio for external communication is to be included.

While the present invention has been described with respect to a limitednumber of embodiments, those skilled in the art will appreciate numerousmodifications and variations therefrom. It is intended that the appendedclaims cover all such modifications and variations as fall within thetrue spirit and scope of this present invention.

A design may go through various stages, from creation to simulation tofabrication. Data representing a design may represent the design in anumber of manners. First, as is useful in simulations, the hardware maybe represented using a hardware description language or anotherfunctional description language. Additionally, a circuit level modelwith logic and/or transistor gates may be produced at some stages of thedesign process. Furthermore, most designs, at some stage, reach a levelof data representing the physical placement of various devices in thehardware model. In the case where conventional semiconductor fabricationtechniques are used, the data representing the hardware model may be thedata specifying the presence or absence of various features on differentmask layers for masks used to produce the integrated circuit. In anyrepresentation of the design, the data may be stored in any form of amachine readable medium. A memory or a magnetic or optical storage suchas a disc may be the machine readable medium to store informationtransmitted via optical or electrical wave modulated or otherwisegenerated to transmit such information. When an electrical carrier waveindicating or carrying the code or design is transmitted, to the extentthat copying, buffering, or re-transmission of the electrical signal isperformed, a new copy is made. Thus, a communication provider or anetwork provider may store on a tangible, machine-readable medium, atleast temporarily, an article, such as information encoded into acarrier wave, embodying techniques of embodiments of the presentinvention.

A module as used herein refers to any combination of hardware, software,and/or firmware. As an example, a module includes hardware, such as amicrocontroller, associated with a non-transitory medium to store codeadapted to be executed by the microcontroller. Therefore, reference to amodule, in one embodiment, refers to the hardware, which is specificallyconfigured to recognize and/or execute the code to be held on anon-transitory medium. Furthermore, in another embodiment, use of amodule refers to the non-transitory medium including the code, which isspecifically adapted to be executed by the microcontroller to performpredetermined operations. And as can be inferred, in yet anotherembodiment, the term module (in this example) may refer to thecombination of the microcontroller and the non-transitory medium. Oftenmodule boundaries that are illustrated as separate commonly vary andpotentially overlap. For example, a first and a second module may sharehardware, software, firmware, or a combination thereof, whilepotentially retaining some independent hardware, software, or firmware.In one embodiment, use of the term logic includes hardware, such astransistors, registers, or other hardware, such as programmable logicdevices.

Use of the phrase ‘to’ or ‘configured to,’ in one embodiment, refers toarranging, putting together, manufacturing, offering to sell, importingand/or designing an apparatus, hardware, logic, or element to perform adesignated or determined task. In this example, an apparatus or elementthereof that is not operating is still ‘configured to’ perform adesignated task if it is designed, coupled, and/or interconnected toperform said designated task. As a purely illustrative example, a logicgate may provide a 0 or a 1 during operation. But a logic gate‘configured to’ provide an enable signal to a clock does not includeevery potential logic gate that may provide a 1 or 0. Instead, the logicgate is one coupled in some manner that during operation the 1 or 0output is to enable the clock. Note once again that use of the term‘configured to’ does not require operation, but instead focus on thelatent state of an apparatus, hardware, and/or element, where in thelatent state the apparatus, hardware, and/or element is designed toperform a particular task when the apparatus, hardware, and/or elementis operating.

Furthermore, use of the phrases ‘capable of/to,’ and or ‘operable to,’in one embodiment, refers to some apparatus, logic, hardware, and/orelement designed in such a way to enable use of the apparatus, logic,hardware, and/or element in a specified manner. Note as above that useof to, capable to, or operable to, in one embodiment, refers to thelatent state of an apparatus, logic, hardware, and/or element, where theapparatus, logic, hardware, and/or element is not operating but isdesigned in such a manner to enable use of an apparatus in a specifiedmanner.

A value, as used herein, includes any known representation of a number,a state, a logical state, or a binary logical state. Often, the use oflogic levels, logic values, or logical values is also referred to as 1'sand 0's, which simply represents binary logic states. For example, a 1refers to a high logic level and 0 refers to a low logic level. In oneembodiment, a storage cell, such as a transistor or flash cell, may becapable of holding a single logical value or multiple logical values.However, other representations of values in computer systems have beenused. For example the decimal number ten may also be represented as abinary value of 1010 and a hexadecimal letter A. Therefore, a valueincludes any representation of information capable of being held in acomputer system.

Moreover, states may be represented by values or portions of values. Asan example, a first value, such as a logical one, may represent adefault or initial state, while a second value, such as a logical zero,may represent a non-default state. In addition, the terms reset and set,in one embodiment, refer to a default and an updated value or state,respectively. For example, a default value potentially includes a highlogical value, i.e. reset, while an updated value potentially includes alow logical value, i.e. set. Note that any combination of values may beutilized to represent any number of states.

The embodiments of methods, hardware, software, firmware or code setforth above may be implemented via instructions or code stored on amachine-accessible, machine readable, computer accessible, or computerreadable medium which are executable by a processing element. Anon-transitory machine-accessible/readable medium includes any mechanismthat provides (i.e., stores and/or transmits) information in a formreadable by a machine, such as a computer or electronic system. Forexample, a non-transitory machine-accessible medium includesrandom-access memory (RAM), such as static RAM (SRAM) or dynamic RAM(DRAM); ROM; magnetic or optical storage medium; flash memory devices;electrical storage devices; optical storage devices; acoustical storagedevices; other form of storage devices for holding information receivedfrom transitory (propagated) signals (e.g., carrier waves, infraredsignals, digital signals); etc, which are to be distinguished from thenon-transitory mediums that may receive information there from.

Instructions used to program logic to perform embodiments of theinvention may be stored within a memory in the system, such as DRAM,cache, flash memory, or other storage. Furthermore, the instructions canbe distributed via a network or by way of other computer readable media.Thus a machine-readable medium may include any mechanism for storing ortransmitting information in a form readable by a machine (e.g., acomputer), but is not limited to, floppy diskettes, optical disks,Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks,Read-Only Memory (ROMs), Random Access Memory (RAM), ErasableProgrammable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), magnetic or optical cards, flashmemory, or a tangible, machine-readable storage used in the transmissionof information over the Internet via electrical, optical, acoustical orother forms of propagated signals (e.g., carrier waves, infraredsignals, digital signals, etc.). Accordingly, the computer-readablemedium includes any type of tangible machine-readable medium suitablefor storing or transmitting electronic instructions or information in aform readable by a machine (e.g., a computer)

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present invention. Thus, theappearances of the phrases “in one embodiment” or “in an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

In the foregoing specification, a detailed description has been givenwith reference to specific exemplary embodiments. It will, however, beevident that various modifications and changes may be made theretowithout departing from the broader spirit and scope of the invention asset forth in the appended claims. The specification and drawings are,accordingly, to be regarded in an illustrative sense rather than arestrictive sense. Furthermore, the foregoing use of embodiment andother exemplarily language does not necessarily refer to the sameembodiment or the same example, but may refer to different and distinctembodiments, as well as potentially the same embodiment.

The systems, methods, and apparatuses can include one or a combinationof the following examples:

Example 1 is an apparatus comprising a controller and a command queue tobuffer incoming write requests into the apparatus. The controller is toreceive, from a client across a link, a non-posted write request in atransaction layer packet (TLP) to the command queue; determine that thecommand queue can accept the non-posted write request; generate acompletion message with a completion status bit set to successfulcompletion (SC); and transmit, to the client across the link, thecompletion message indicating that the non-posted write request wasaccepted into the command queue.

Example 2 may include the subject matter of example 1, wherein thenon-posted write request comprises an deferred memory write (DMWr)request message.

Example 3 may include the subject matter of any of examples 2-3, thecontroller to receive a second non-posted write request in a second TLP;determine that the command queue is full; generate a completion messagewith a completion status bit set to memory request retry status (MRS);and transmit, to the client across the link, the completion messageindicating that the non-posted write request was rejected into thecommand queue.

Example 4 may include the subject matter of example 3, the controller toreceive a third TLP comprising a retry of the second non-posted writerequest; determine that the command queue can accept the secondnon-posted write request; generate a completion message with acompletion status bit set to successful completion (SC); and transmit,to the client across the link, the completion message indicating thatthe non-posted write request was accepted into the command queue.

Example 5 may include the subject matter of any of examples 1-3, whereinthe apparatus comprises an input/output device, such as an accelerator.

Example 6 may include the subject matter of any of examples 1-5, whereinthe non-posted write request is received in a transaction layer packet(TLP) that comprises a type field indicating the acknowledged memorywrite request.

Example 7 may include the subject matter of example 6, wherein the TLPcomprises a completion field that indicates completion without data foran acknowledged memory write completion.

Example 8 may include the subject matter of any of examples 1-7, whereinthe link is based on a Peripheral Component Interconnect Express (PCIe)protocol.

Example 9 is a system comprising a host device comprising a portresiding at the host device, the port to transmit a TLP containing anon-posted write request to the I/O device across the link; and aninput/output (I/O) device coupled to the port across a link. The I/Odevice can receive the TLP comprising the non-posted write request fromacross the link, determine that the command queue has space available toaccept the non-posted write request, generate a completion message witha completion status bit set to successful completion (SC). The port totransmit, to a client across the link, the completion message indicatingthat the non-posted write request was accepted into the command queue.

Example 10 may include the subject matter of example 9, wherein thenon-posted write request is a first non-posted write request. Totransmit a second TLP comprising a second non-posted write request tothe I/O device. The I/O device to receive the second non-posted writerequest, determine that the command queue at the I/O device is full, andgenerate a completion message with a completion status bit set to memoryrequest retry status (MRS) for transmission by the port to the clientacross the link, the completion message indicating that the non-postedwrite request was rejected into the command queue. The port to forwardthe message indicating the completion message of the non-posted writerequest to a link partner of the I/O device.

Example 11 may include the subject matter of any of examples 9, whereinthe non-posted write request is a first non-posted write request.

Example 12 may include the subject matter of example 11, wherein theport is a first port, the host device comprising a second port, thesecond port comprising an egress blocking enabled, the second port toreceive a second non-posted write request from a link partner; andtransmit a completion message that comprises a status of unsupportedrequest status identifier.

Example 13 may include the subject matter of example 11, wherein the I/Odevice is to receive a second non-posted write request, the secondnon-posted write request comprising a transaction layer packet that iscorrupted; and transmit a completion message that includes anunsupported request status indicator to the first port.

Example 14 may include the subject matter of example 11, wherein the I/Odevice is to receive a second non-posted write request; determine thatthe second non-posted write request comprises an uncorrectable error;and transmit a completer abort message to the port.

Example 15 may include the subject matter of example 11, wherein the I/Odevice is to receive a second non-posted write request; determine thatthe second non-posted write request comprises an unsupported type oroperand; and transmit a completion message with an unsupported requeststatus indicator to the port.

Example 16 may include the subject matter of any of examples 9-15,wherein the I/O device comprises an accelerator device.

Example 17 may include the subject matter of any of examples 9-16,wherein the non-posted write request comprises an deferred memory write(DMWr) request.

Example 18 may include the subject matter of any of examples 9-17,wherein the command queue comprises a shared work queue (SWQ) and thenon-posted write request is received at the SWQ of the I/O device.

Example 19 may include the subject matter of any of examples 9-18,wherein the link is based on a Peripheral Component Interconnect Express(PCIe) protocol.

Example 20 is a computer-implemented method comprising receiving, at aninput/output (I/O) device from a client across a link, a non-postedwrite request in a transaction layer packet (TLP) to the command queue;determining, by a controller of the I/O device, that the command queuecan accept the non-posted write request; generating a completion messagewith a completion status bit set to successful completion (SC); andtransmitting, to the client across the link, the completion messageindicating that the non-posted write request was accepted into thecommand queue.

Example 21 may include the subject matter of example 20, wherein thenon-posted write request comprises a deferred memory write (DMWr)request message.

Example 22 may include the subject matter of any of examples 20-21, andmay also include receiving, at the I/O device, a second non-posted writerequest in a second TLP; determining, by a controller of the I/O device,that the command queue is full; generating a completion message with acompletion status bit set to memory request retry status (MRS); andtransmitting, to the client across the link, the completion messageindicating that the non-posted write request was rejected into thecommand queue.

Example 23 may include the subject matter of example 22, and may alsoinclude receiving a third TLP comprising a retry of the secondnon-posted write request; determining that the command queue can acceptthe second non-posted write request; generating a completion messagewith a completion status bit set to SC; and transmitting the completionmessage to the link partner.

Example 24 may include the subject matter of any of examples 20-23, andmay also include receiving a second non-posted write request;determining that the second non-posted write request comprises anuncorrectable error; and transmit a completer abort message to the linkpartner.

Example 25 may include the subject matter of any of examples 20-24, andmay also include receiving a second non-posted write request;determining that the non-posted write request comprises an unsupportedtype or operand; and transmitting a completion message with anunsupported request status indicator to the link partner.

Example 26 is an apparatus that includes a command queue to bufferincoming work requests and a means for determining, from a receivedtransaction layer packet, a deferred memory write (DMWr) request and oneor more response messages to the DMWr based on the status of the commandqueue.

What is claimed is:
 1. An apparatus comprising: a controller; anon-volatile memory; and a command queue to buffer incoming writerequests into the non-volatile memory from multiple clients; thecontroller to: receive, from a client across a link, a non-posted writerequest in a transaction layer packet (TLP) to the command queue,wherein the non-posted write request comprises a Deferrable Memory Write(DMWr) request message, wherein the TLP comprises a type field thatindicates that the non-posted write request is a DMWr request, the typefield comprising a [4:0] b encoding of 11011; determine that the commandqueue can accept the non-posted write request; generate a completionmessage; set a bit in a completion status field of the completionmessage to a value that indicates a successful completion (SC) thatindicates that the non-posted write request was accepted into thecommand queue; and transmit, to the client across the link, thecompletion message with the SC that indicates that the non-posted writerequest was accepted into the command queue.
 2. The apparatus of claim1, the controller to: receive a second non-posted write request in asecond TLP; determine that the command queue is full; generate acompletion message; set a bit in a completion status field of thecompletion message to a value that indicates a memory request retrystatus (MRS) that indicates that the command queue is full; and transmitthe completion message that includes the MRS to the client across thelink; wherein the encoding for the MRS comprises a [2:0] b encoding of101.
 3. The apparatus of claim 2, the controller to: receive a third TLPcomprising a retry of the second non-posted write request; determinethat the command queue can accept the second non-posted write request;generate a completion message; set a bit in a completion status field ofthe completion message to a value that indicates an SC that indicatesthat the non-posted write request was accepted into the command queue;and transmit the completion message with the SC to the client across thelink.
 4. The apparatus of claim 1, wherein the apparatus comprises aninput/output device.
 5. The apparatus of claim 1, wherein the TLPcomprises a completion field that indicates completion without data foran acknowledged memory write completion.
 6. The apparatus of claim 1,wherein the link is based on a Peripheral Component Interconnect Express(PCIe) protocol.
 7. The apparatus of claim 1, wherein the completionmessage comprises a [2:0] b encoding of 000 to indicate the SC.
 8. Theapparatus of claim 1, wherein apparatus comprises a hardwareaccelerator.
 9. A system comprising: a host device comprising a portresiding at the host device, the port to transmit a transaction layerpacket (TLP) comprising a non-posted write request to the I/O deviceacross a link, wherein the non-posted write request comprises aDeferrable Memory Write (DMWr) request message, wherein the TLPcomprises a type field that indicates that the non-posted write requestis a DMWr request, the type field comprising a [4:0] b encoding of11011; and an input/output (I/O) device coupled to the port across thelink, the I/O device to: receive the TLP comprising the non-posted writerequest from across the link, determine that a command queue has spaceavailable to accept the non-posted write request, generate a completionmessage; set a completion status of the completion message to SuccessfulCompletion (SC) that indicates that the non-posted write request wasaccepted into the command queue, and transmit the completion message tothe port; the port to transmit the SC message to a link partner of thehost device.
 10. The system of claim 9, wherein the non-posted writerequest is a first non-posted write request; the port to transmit asecond TLP comprising a second non-posted write request to the I/Odevice; the I/O device to: receive the second non-posted write request,determine that the command queue at the I/O device is full, generate acompletion message with a completion status bits set to memory requestretry status (MRS), the MRS encoded as [2:0] b having a value of 101 andtransmit to the port across the link the completion message; the port toforward the message that indicates the retry of the non-posted writerequest to a link partner of the I/O device.
 11. The system of claim 10,wherein the completion message comprises a [2:0] b encoding of 000 toindicate the SC.
 12. The system of claim 9, wherein the non-posted writerequest is a first non-posted write request.
 13. The system of claim 12,wherein the port is a first port, the host device comprising a secondport, the second port comprising an egress blocking enabled, the secondport to: receive a second non-posted write request from a link partner;and transmit a completion message that comprises a status of unsupportedrequest status identifier.
 14. The system of claim 12, wherein the I/Odevice is to: receive a second non-posted write request, the secondnon-posted write request comprising a transaction layer packet that iscorrupted; and transmit a completion message that includes anunsupported request status indicator to the first port.
 15. The systemof claim 12, wherein the I/O device is to: receive a second non-postedwrite request; determine that the second non-posted write requestcomprises an uncorrectable error; and transmit a completer abort messageto the port.
 16. The system of claim 12, wherein the I/O device is to:receive a second non-posted write request; determine that the secondnon-posted write request comprises an unsupported type or operand; andtransmit a completion message with an unsupported request statusindicator to the port.
 17. The system of claim 9, wherein the I/O devicecomprises an accelerator device.
 18. The system of claim 9, wherein thecommand queue comprises a shared work queue (SWQ) and the non-postedwrite request is received at the SWQ of the I/O device.
 19. The systemof claim 9, wherein the link is based on a Peripheral ComponentInterconnect Express (PCIe) protocol.
 20. A computer-implemented methodcomprising: receiving, at an input/output (I/O) device from a clientacross a link, a non-posted write request in a transaction layer packet(TLP) to the command queue, wherein the non-posted write requestcomprises an Deferrable Memory Write (DMWr) request message, wherein theTLP comprises a type field that indicates that the non-posted writerequest is a DMWr request, the type field comprising a [4:0] b encodingof 11011; determining, by a controller of the I/O device, that thecommand queue can accept the non-posted write request; generating acompletion message with a completion status bit set to successfulcompletion (SC); and transmitting, to the client across the link, thecompletion message.
 21. The method of claim 20, further comprising:receiving, at the I/O device, a second non-posted write request in asecond TLP; determining, by a controller of the I/O device, that thecommand queue is full; generating a completion message with a completionstatus bit set to memory request retry status (MRS); and transmitting,to the client across the link, the completion message.
 22. The method ofclaim 21, further comprising: receiving a third TLP comprising a retryof the second non-posted write request; determining that the commandqueue can accept the second non-posted write request; generating acompletion message with a completion status bit set to SC; andtransmitting, to the client across the link, the completion message. 23.The method of claim 20, further comprising: receiving a secondnon-posted write request; determining that the second non-posted writerequest comprises an uncorrectable error; and transmit a completer abortmessage to the link partner.
 24. The method of claim 20, furthercomprising: receiving a second non-posted write request; determiningthat the non-posted write request comprises an unsupported type oroperand; and transmitting a completion message with an unsupportedrequest status indicator to the link partner.
 25. The method of claim20, wherein the completion message comprises a [2:0] b encoding of 000to indicate the SC.